>> This is, in any case, how I'd handle this one. Always install a >> macports.conf.default and add some logic to load the two in order >> (macports.conf should, in fact, be optional). > > Great, and after we solve this, we'll do the same for all the > software one could install using MacPorts, right? :-D
Sure, why not - other package systems do it already... ? http://trac.macports.org/projects/macports/ticket/12797 http://trac.macports.org/projects/macports/ticket/2365 --anders _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
