gmp's archive_site in Portfile disables custom archive_sites

Chris Jones jonesc at
Thu Jan 5 16:08:14 UTC 2017


when you say 'breaks your setup' what exactly do you mean ?

Presumably the first machine, that creates the local binaries runs just 
fine, but then the second doesn't use these for this one port, and 
attempts to build again from source ? If correct, is this really a 
problem ? From the discussion in the ticket this is exactly what is 
wanted for this port, as it compiles very specifically for the machine 
it is to be used on. You *want* it to therefore build from source on 
each and every machine.


On 05/01/17 14:23, Peter Brommer wrote:
> Hi,
> it appears that gmp @6.1.2_0 breaks my macports setup, due to its use of “archive_sites” in the Portfile (to avoid installing from precompiled binaries).
> I have two Macs, and I use the setup described in - one machine creates the local binaries not available from macports, the other one uses them via a customised archive_sites.conf.
> gmp (and maybe other ports) unsets archive_sites to avoid installing from binaries (as discussed in, so it ignores my custom archive_site (aside: in principle, it should fail as I request binary-only with port -b upgrade, but if I read correctly that will be addressed in a future macports release). However, after building, installing and activating gmp, macports no longer used my local archive_site, but falls back to the default archive_sites.
> I’m not sure if this is a bug, and I have a hard time reproducing it, as the second time I run the command, gmp is already upgraded, and it keeps using my local archive_site. Should I still file this as a bug? And against what?
> Cheers,
> Peter

More information about the macports-users mailing list