On Tue, Nov 10, 2015 at 7:21 PM, Joshua Root wrote: > On 2015-11-11 00:26 , Mojca Miklavec wrote: >> If we start including macosx_deployment_target, macosx_sdk, prefix, >> applications_dir, frameworks_dir, ... we'll sooner or later end up in >> an exponential mess > > These are the type of settings that are associated with an entire source > in archive_sites.conf, because all the archives from a given source will > have them set the same. If any of these settings for a source don't > match the ones used locally, the source is simply not used. Putting > cxx_stdlib in here as well would be a good fit.
Are you saying that putting cxx_stdlib libc++ inside archive_sites.conf instead of macports.conf (and possibly making some additional changes in the code) would automatically make sure that one would not have to write an explicit: buildfromsource always and MacPorts would make sure that one would not fetch the binary from a server with binaries using different settings? In a way that would make sense to me as well, but I don't exactly understand how everything works. Mojca _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
