[MacPorts] #38117: active_variants: allow multiple port names to be specified
#38117: active_variants: allow multiple port names to be specified --------------------------+-------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: --------------------------+-------------------------------- Currently, I can use e.g.: {{{ require_active_variants pango x11 }}} to require that the pango port be installed with the +x11 variant. However it should be permitted for users to use the pango-devel port instead. We need a way to tell require_active_variants of alternate port names. Perhaps this syntax should be supported: {{{ require_active_variants {pango pango-devel} x11 }}} -- Ticket URL: <https://trac.macports.org/ticket/38117> MacPorts <http://www.macports.org/> Ports system for Mac OS
#38117: active_variants: allow multiple port names to be specified ---------------------------+-------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: | ---------------------------+-------------------------------- Comment (by ryandesign@…): Even nicer might be if we could just use normal dependency specifiers, e.g.: {{{ require_active_variants path:lib/pkgconfig/pango.pc:pango x11 }}} -- Ticket URL: <https://trac.macports.org/ticket/38117#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#38117: active_variants: allow multiple port names to be specified ---------------------------+-------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: | ---------------------------+-------------------------------- Comment (by egall@…): This would make sense considering you can already specify multiple variants with this. If you can specify multiple variants with `require_active_variants`, I would think it would be theoretically pretty easy to take the code for specifying multiple variants and turn it into code for specifying multiple ports. -- Ticket URL: <https://trac.macports.org/ticket/38117#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
#38117: active_variants: allow multiple port names to be specified ---------------------------+-------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: | ---------------------------+-------------------------------- Comment (by cal@…): Patches welcome, in this case :) I think it might actually be easier to move this into base at this point, because base probably has an easy way to resolve path-style (and other) dependencies. -- Ticket URL: <https://trac.macports.org/ticket/38117#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
#38117: active_variants: allow multiple port names to be specified ---------------------------+---------------------- Reporter: ryandesign@… | Owner: cal@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: | ---------------------------+---------------------- Changes (by cal@…): * owner: macports-tickets@… => cal@… * status: new => assigned -- Ticket URL: <https://trac.macports.org/ticket/38117#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X
#38117: active_variants: allow multiple port names to be specified ---------------------------+---------------------- Reporter: ryandesign@… | Owner: cal@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: | ---------------------------+---------------------- Comment (by michaelld@…): I posted about this issue on the [https://lists.macosforge.org/pipermail /macports-dev/2013-April/022513.html mp-dev list]. I've attached the patch here, too; it implements the "path:...:port" version, just like a dependency. -- Ticket URL: <https://trac.macports.org/ticket/38117#comment:7> MacPorts <http://www.macports.org/> Ports system for OS X
#38117: active_variants: allow multiple port names to be specified ---------------------------+-------------------- Reporter: ryandesign@… | Owner: cal@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: fixed | Keywords: Port: | ---------------------------+-------------------- Changes (by cal@…): * status: assigned => closed * resolution: => fixed Comment: r104849. -- Ticket URL: <https://trac.macports.org/ticket/38117#comment:8> MacPorts <http://www.macports.org/> Ports system for OS X
#38117: active_variants: allow multiple port names to be specified ---------------------------+-------------------- Reporter: ryandesign@… | Owner: cal@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: fixed | Keywords: Port: | ---------------------------+-------------------- Comment (by cal@…): I've fixed the ports that were incorrectly limiting the dependencies to a single port due to the active_variants checks in - r104850: gtk3 - r104851: gtk2 - r104852: py-cairo - r104853: pango - r104854: pango-devel -- Ticket URL: <https://trac.macports.org/ticket/38117#comment:9> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts