[MacPorts] #44267: root6: Portfile parse problem when root5 installed
MacPorts
noreply at macports.org
Mon Jul 7 09:45:41 PDT 2014
#44267: root6: Portfile parse problem when root5 installed
---------------------+---------------------
Reporter: mf2k@… | Owner: mojca@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.3.99
Resolution: | Keywords:
Port: root6 |
---------------------+---------------------
Comment (by jonesc@…):
Hi,
I cannot pre-produce your 'failed to parse' error, but I can reproduce the
general issue that various port commands don't given much useful
information once root5 is installed with +python27, and with root6 having
that variant enabled by default
{{{
macmini ~ > sudo port install root6
Error: Cannot install root6 with +python27 variant
Error: Unable to open port: root5 port is already installed with +python27
and both cannot be active at once. Pick a different python variant.
macmini ~ > sudo port info root6
Error: Cannot install root6 with +python27 variant
Error: Unable to open port: root5 port is already installed with +python27
and both cannot be active at once. Pick a different python variant.
macmini ~ > sudo port variants root6
Error: Cannot install root6 with +python27 variant
Error: Unable to open port: root5 port is already installed with +python27
and both cannot be active at once. Pick a different python variant.
}}}
I have a patch that proves moving the check to a later phases fixes the
above. It worked for me moving it to pre-activate, but this is not ideal
as it would mean in some cases the user would only find out after the long
build. I couldn't though find a phase that both worked and avoided this...
? I attach the patch just for reference...
Chris
--
Ticket URL: <https://trac.macports.org/ticket/44267#comment:3>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list