#37980: Trunk breaks ports using llvm-gcc without automatically adding a dependency on macports-llvm-gcc --------------------------------+------------------------ Reporter: macsforever2000@… | Owner: jeremyhu@… Type: defect | Status: reopened Priority: Normal | Milestone: Component: base | Version: 2.1.99 Resolution: | Keywords: Port: mysql5 mysql51 | --------------------------------+------------------------ Comment (by cal@…): Replying to [comment:12 jeremyhu@…]:
Leaving it as 4.6 allows developers to see what will happen when the next version of XCode is released, so developers have time to react.
TBH, we haven't cared about future Xcode updates previously, I don't see why we're handling this one different. Go ahead and implement a deprecation warning along with suggestions on how to make the port future proof, if you want, but breaking stuff completely is not a good way to handle this, IMO. At the moment all we have is breakage of otherwise well-working ports and no clear strategy on how to fix the breakage (other than in trunk, where it was not fixed so far). Are you suggesting we should add the hack ryan commited above to all affected ports? That doesn't sound like a good solution to me.
If you want to be coddled and don't want to actually fix bugs, you can use the 2.1 branch. If you want to actually find and fix bugs before they impact our users, use trunk.
It might have escaped your attention, but I am actually doing development work of MacPorts base on trunk and I am actually fixing bugs. See the Changelog. Pointing people to bugs without having a proper way to solve them sounds useless to me, though. It's annoying. -- Ticket URL: <https://trac.macports.org/ticket/37980#comment:13> MacPorts <http://www.macports.org/> Ports system for Mac OS