#34477: cloog depends on isl but cloog and isl conflict -------------------------------------+-------------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.0 Keywords: | Port: cloog isl -------------------------------------+-------------------------------------- Comment(by ecronin@…): When I asked about this on -dev a while back the answer was that 0.16.3_0 epoch 0 and 0.16.3_0 epoch 1 are assumed to have identical contents, and that it is intentional that they won't show as outdated: http://old.nabble.com/Re%3A--91865--trunk-dports-science-netcdf-cxx- Portfile-p33679541.html:
It doesn't matter, by definition. A higher epoch just tells you that an older-looking (but different) version is actually newer. If name,version,revision,variants are all the same, it's the same software.
This means you can upgrade a port from 1.0 to 1.1, and then if there are problems with 1.1, revert to 1.0 by increasing the epoch, and nobody who hadn't upgraded yet has to rebuild.
So you need to update to a revision that's never been used before for port to think the epoch 1 version is newer... I still think this is very confusing behavior, but I don't have the statistics on how many times epoch is upped and a pure revert happens vs the Portfiles not being identical for the same version between epochs. -- Ticket URL: <https://trac.macports.org/ticket/34477#comment:8> MacPorts <http://www.macports.org/> Ports system for Mac OS