Opened 8 years ago

Last modified 8 years ago

#38112 new enhancement

RFE: add a "depends_pkg" type of dependency

Reported by: cooljeanius (Eric Gallager) Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: base Version: 2.1.3
Keywords: Cc:
Port:

Description

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
}

Change History (4)

comment:1 Changed 8 years ago by mf2k (Frank Schima)

Component: portsbase

comment:2 Changed 8 years ago by jmroot (Joshua Root)

So installing a pkg of the port would give you something different than port install? That doesn't seem like a very good idea.

comment:3 Changed 8 years ago by cooljeanius (Eric Gallager)

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?

comment:4 Changed 8 years ago by ryandesign (Ryan Schmidt)

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.

Note: See TracTickets for help on using tickets.