After-thought: this is of course counter-productive for custom port trees that
do not override the main tree but in which you want to use a custom version of
an existing PortGroup.
One could think of making an optional check using `getportresourcepath` before
scanning over all port trees; the
Thanks again, this patch seems to do what I want:
https://github.com/RJVB/macstrop/blob/master/sysutils/MacPorts/files/patch-hierarchical-portgroup-search.diff
R.
On 2018-06-12 21:20, René J.V. Bertin wrote:
> Rainer Müller wrote on 20180612::18:22:46 re: "Re: PortGroup vs. Portfile
> search strategy"
>
> Hi,
>
>> The implementation of PortGroup is here:
>> https://github.com/macports/macports-base/blob/master/src/port1.0/portutil.tcl#L2509-L2535
>
>
