Archive behavior on epoch-bump

Clemens Lang cal at macports.org
Sun Aug 25 02:50:05 PDT 2013


Hi,

can somebody with more insight into the binary archives shed light on
what will happen if I epoch-bump a number of ports, but neither change
version nor revision? Will users end up downloading an old copy of the
port from packages.macports.org in that case? It seems to me the epoch
isn't encoded in the filename for our binary archives (see libedit[1] as
an example).

The background here is that all haskell packages need to be rebuilt
whenever GHC is updated. Can I avoid touching each port by adding an
epoch line to the Haskell PortGroup? I suppose that might not be enough,
because portindex wouldn't reindex the changed ports then, right? What's
the best way to overcome this situation?

[1] http://packages.macports.org/libedit/
-- 
Clemens Lang



More information about the macports-dev mailing list