scope of "local" PortGroup definition files

René J.V. Bertin rjvbertin at
Fri Jan 9 04:23:06 PST 2015

On Friday January 09 2015 12:18:16 Rainer Müller wrote:

> > Is that correct and if so, is there a way to override the definitions
> > on a global basis?
> Port groups not found in the current ports tree are being looked up in
> the ports tree marked with [default] in sources.conf.

That's not what I'm seeing. What I'm seeing, at least not with the compiler-blacklist port group on linux. I've changed my "local" copy to skip the version parsing (= return early) when `uname` doesn't return Darwin, instead of raising an error because Linux clang -v output doesn't correspond to the expected format. This works for my own ports in that local repo, but ports in the default tree continue to raise the error unless I apply the same change in the default PortGroup definition.

NB: my only reason to "use" MacPorts on Linux is to be able to do some minimum portfile development/maintenance from there, without having to log in to OS X.
NB2: my mod uses uname because for some reason ${os.platform} is not available from the version parsing procedure.


More information about the macports-dev mailing list