#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 mojca@…): "Failed to parse root" looks like a bug, but how should this be implemented / what behaviour would you expect? If you manually enabled `+python27` for `root5`, that conflicts with `root6` with `python27` enabled by default. What should the portfile do in cases when python is already installed with `root5`? -- Ticket URL: <https://trac.macports.org/ticket/44267#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X

#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

#44267: root6: Portfile parse problem when root5 installed ---------------------+--------------------- Reporter: mf2k@… | Owner: mojca@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.99 Resolution: fixed | Keywords: Port: root6 | ---------------------+--------------------- Comment (by mojca@…): But that's "slightly suboptimal". If you have `root5 +python27` installed, your machine could spend 4 hours compiling `root6 +python27` (hopefully less), only to tell you that the variant conflicts with `root5` just before activation. Personally I'm not a big fan of this solution (even though I admit that it at least solves one weird problem). I would ask others for help. -- Ticket URL: <https://trac.macports.org/ticket/44267#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X

#44267: root6: Portfile parse problem when root5 installed ---------------------+--------------------- Reporter: mf2k@… | Owner: mojca@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.99 Resolution: fixed | Keywords: Port: root6 | ---------------------+--------------------- Comment (by mf2k@…): I don't see that as a big deal. Someone might actually want both versions. They can then switch between the 2 versions by simply deactivating one and activating the other without rebuilding. It's much better than not even being able to see that root6 exists. -- Ticket URL: <https://trac.macports.org/ticket/44267#comment:7> MacPorts <http://www.macports.org/> Ports system for OS X

#44267: root6: Portfile parse problem when root5 installed ---------------------+--------------------- Reporter: mf2k@… | Owner: mojca@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.99 Resolution: fixed | Keywords: Port: root6 | ---------------------+--------------------- Comment (by mojca@…): That is: because it notices conflicting files. I believe that we should figure out how to use the `active_variants` PortGroup here. -- Ticket URL: <https://trac.macports.org/ticket/44267#comment:9> MacPorts <http://www.macports.org/> Ports system for OS X