[MacPorts] #37923: Submission: New variants for the MacPorts port: Allow ports provided by MacPorts to fulfill missing dependencies for it
#37923: Submission: New variants for the MacPorts port: Allow ports provided by MacPorts to fulfill missing dependencies for it ------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: haspatch | Port: MacPorts ------------------------+-------------------------------- Attached is a diff to apply to the Portfile for the MacPorts port. I've linted and tested it and it works. -- Ticket URL: <https://trac.macports.org/ticket/37923> MacPorts <http://www.macports.org/> Ports system for Mac OS
#37923: Submission: New variants for the MacPorts port: Allow ports provided by MacPorts to fulfill missing dependencies for it -------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: haspatch Port: MacPorts | -------------------------+-------------------------------- Comment (by ryandesign@…): Why would we want this? -- Ticket URL: <https://trac.macports.org/ticket/37923#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#37923: Submission: New variants for the MacPorts port: Allow ports provided by MacPorts to fulfill missing dependencies for it -------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: haspatch Port: MacPorts | -------------------------+-------------------------------- Comment (by egall@…): Replying to [comment:1 ryandesign@…]:
Why would we want this?
Well, personally, I want it so that I can be sure that my MacPorts installation is taking advantage of all the latest and greatest things available to it. I bet some other users might want this option, too. -- Ticket URL: <https://trac.macports.org/ticket/37923#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#37923: Submission: New variants for the MacPorts port: Allow ports provided by MacPorts to fulfill missing dependencies for it -------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: haspatch Port: MacPorts | -------------------------+-------------------------------- Changes (by raimue@…): * cc: raimue@… (added) Comment: The MacPorts port is currently only meant to be used for building the MacPorts .dmg and .pkg installers. Maybe it shouldn't even be in the tree, but rather live in base/portmgr. While this proposed patch is a nice experiment on how MacPorts might become self-contained, I don't think this is something that should be done right now and offered to end-users. At the moment, we do not have any fallbacks in case one of the dependencies breaks due to bad linking. What exactly is the intent of this? It only seems to replace the binaries called by MacPorts and does not cover libraries linked to Pextlib or the registry (curl and sqlite3). -- Ticket URL: <https://trac.macports.org/ticket/37923#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
#37923: Submission: New variants for the MacPorts port: Allow ports provided by MacPorts to fulfill missing dependencies for it -------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: haspatch Port: MacPorts | -------------------------+-------------------------------- Comment (by egall@…): Replying to [comment:3 raimue@…]:
The MacPorts port is currently only meant to be used for building the MacPorts .dmg and .pkg installers. Maybe it shouldn't even be in the tree, but rather live in base/portmgr. Fair enough. I was actually thinking the contrib folder, but that works too. It only seems to replace the binaries called by MacPorts and does not cover libraries linked to Pextlib or the registry (curl and sqlite3). curl and sqlite3 added in the latest version. I did just plain sqlite3 instead of tcl-sqlite3 because the latter is broken by #37376. I also left out the `--with-tcl-sqlite3=/opt/local/lib/sqlite3.7.15.1/` flag though because that version number at the end of the directory there looks like it would change often, and I'm not sure how I'd check for that...
-- Ticket URL: <https://trac.macports.org/ticket/37923#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS
#37923: MacPorts: add variant to use MacPorts ports as dependencies --------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: wontfix | Keywords: haspatch Port: MacPorts | --------------------------+-------------------------------- Changes (by ryandesign@…): * cc: ryandesign@… (added) * status: new => closed * type: submission => enhancement * resolution: => wontfix Comment: I really don't think we want any such patch, since the only reason this port exists is so that we can create installer packages of new versions of MacPorts (no user should ever install the MacPorts port directly), and in the installer packages, the MacPorts installation must be self-contained; it cannot be linked with MacPorts-provided libraries that most users who install the disk image won't already have installed. -- Ticket URL: <https://trac.macports.org/ticket/37923#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS
participants (1)
-
MacPorts