[MacPorts] #25040: lilypond 2.12.3 FTB with Python 3 selected
MacPorts
noreply at macports.org
Sun May 30 15:17:06 PDT 2010
#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
----------------------------+-----------------------------------------------
Changes (by ryandesign@…):
* cc: ryandesign@… (added)
Comment:
Replying to [comment:3 gale@…]:
> 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 believe that's what we've done in other ports, so doing so here as well
would be consistent with established practices. Adding a lib dependency on
python25 to make this port's needs clear isn't a bad idea either.
> 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 :)
I have no objection to a general solution, and your PATH idea sounds like
a plausible fix, but python ports are one area of MacPorts I am not
experienced with, and I don't have time to work on this problem now
either. If you have a general suggestion, ideally accompanied by a working
patch for, say, the python portgroups, and can file that in a new ticket,
or maybe bring the matter up for discussion on macports-dev first, that
might help move this forward.
--
Ticket URL: <http://trac.macports.org/ticket/25040#comment:5>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list