[MacPorts] #38112: RFE: add a "depends_pkg" type of dependency
#38112: RFE: add a "depends_pkg" type of dependency -------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: -------------------------+-------------------------------- I'd like to be able to declare a dependency on stuff like `dylibbundler` or `jarbundler` just for the packaging step, so that I could bundle up everything into a single app bundle instead of having the installer put a bunch of stuff in /opt/local. In other words I'd like something like this to work: {{{ depends_pkg dylibbundler pre-pkg { dylibbundler -x ${destroot}${applications_dir}${name}.app/Contents/MacOS/${name} -b -cd -p @executable_path/../libs } }}} -- Ticket URL: <https://trac.macports.org/ticket/38112> MacPorts <http://www.macports.org/> Ports system for Mac OS
#38112: RFE: add a "depends_pkg" type of dependency --------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.3 Resolution: | Keywords: Port: | --------------------------+-------------------------------- Changes (by macsforever2000@…): * component: ports => base -- Ticket URL: <https://trac.macports.org/ticket/38112#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#38112: RFE: add a "depends_pkg" type of dependency --------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.3 Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by jmr@…): So installing a pkg of the port would give you something different than `port install`? That doesn't seem like a very good idea. -- Ticket URL: <https://trac.macports.org/ticket/38112#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#38112: RFE: add a "depends_pkg" type of dependency --------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.3 Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by egall@…): No, this would be for packaging stuff for users that don't have MacPorts installed. Isn't that what the `port pkg` command is for in the first place? -- Ticket URL: <https://trac.macports.org/ticket/38112#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
#38112: RFE: add a "depends_pkg" type of dependency --------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.3 Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by ryandesign@…): Yes but right now "port pkg" runs "port destroot", then creates a package of that destroot. That's what we want; that's what ports do. I can see the value in what you're talking about, if I wanted to distribute some standalone packages, and I might use that technique (running dylibbundler in pre-pkg) but I wouldn't commit that to the main ports tree (I'd keep private modified ports with those changes). And since I'd only be using this on my system, it wouldn't be a problem for me to need to manually install dylibbundler first. -- Ticket URL: <https://trac.macports.org/ticket/38112#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS
participants (1)
-
MacPorts