[macports-ports] 02/02: libgcc-devel: Add direct conflict with libgccX providing primary default runtime

Chris Jones jonesc at hep.phy.cam.ac.uk
Mon May 6 16:46:34 UTC 2019

Previous message: [macports-ports] 01/02: libgcc: remove force deactivation of libgccX on deactivation. No longer needed as libgccX now directly conflicts with libgcc-devel
Next message: [macports-ports] branch master updated: libgcc: rev-bump needed to pick up previous deactivate change
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-changes/attachments/20190506/aee1b6c4/attachment.html>

Previous message: [macports-ports] 01/02: libgcc: remove force deactivation of libgccX on deactivation. No longer needed as libgccX now directly conflicts with libgcc-devel
Next message: [macports-ports] branch master updated: libgcc: rev-bump needed to pick up previous deactivate change
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the macports-changes mailing list