#25040: lilypond 2.12.3 FTB with Python 3 selected ----------------------------+----------------------------------------------- Reporter: gale@… | Owner: snc@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.2 Keywords: | Port: lilypond ----------------------------+----------------------------------------------- Comment(by gale@…): Replying to [comment:2 snc@…]:
If I'm reading this correctly, there are two issues: the program doesn't build against a specific version of python and nothing prevents python3x from satisfying the dependency.
No, not exactly. From the dependency point of view, the port is pulling in a good version of python, python25. python3x does not play any role at all there. The problem is that even though python25 is correctly pulled in as a dependency by the port file, the build proceeds to ignore it. It runs python31 instead, causing it to fail. That is because the build scripts don't call up version 2.5 of python explicitly. They just run python. So the version of python that will actually run is totally independent of the port file. It depends instead on whatever the user happened to set as the default version of python using the python_select port. Or possibly even no python at all will run if the user never used python_select. So I guess another fix would be to go through the build system of this port - makefiles, scripts, and python file shell bangs - and patch them all to run python25 explicitly. I'm suggesting that maybe the time has come to implement a general solution that will provide an easy fix for all ports that have this problem. Instead of hunting for a port-specific hack each time. But if the MacPorts team decides against that and just fixes this port, I'll happily install it :) -- Ticket URL: <http://trac.macports.org/ticket/25040#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS