scope of "local" PortGroup definition files

Bradley Giesbrecht pixilla at macports.org
Fri Jan 9 07:28:43 PST 2015


On Jan 9, 2015, at 4:32 AM, René J.V. Bertin <rjvbertin at gmail.com> wrote:

> Correction: 
> 
> This is not limited to the compiler blacklist portgroup, nor to Linux.
> 
> Exactly as I feared, my changes to the qt4, qt5 and kde4 portgroups need to be copied to the portgroup directory in the default tree if they are to be visible to all ports and not just to the ports in the local repository.

Is your local tree in sources.conf?
grep -v -E "(^ *#|^$)" /opt/local/etc/macports/sources.conf

> Which means that every selfupdate will undo any changes you might have applied.
> 
> Out of curiosity, what if I set my local repository to be the default? Will selfupdate update that tree, or will it continue to update the one under ${prefix}/var/macports/source/.... ?

If you used svn instead of rsync port sync you would not experience this overwrite issue.

Regards,
Bradley Giesbrecht (pixilla)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20150109/5eadda8b/attachment.sig>


More information about the macports-dev mailing list