[MacPorts] #37853: RFE: "port provides" should return a different message when used on files provided by base
#37853: RFE: "port provides" should return a different message when used on files provided by base -------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.2 Keywords: | Port: -------------------------+-------------------------------- It just seems odd that {{{ port provides `which port` }}} should return: {{{ /opt/local/bin/port is not provided by a MacPorts port. }}} I mean, technically, that's true, it isn't technically provided by a port, but still, shouldn't it at least say something about that file being part of base? -- Ticket URL: <https://trac.macports.org/ticket/37853> MacPorts <http://www.macports.org/> Ports system for Mac OS
#37853: RFE: "port provides" should return a different message when used on files provided by base --------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.2 Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by ryandesign@…): I don't think we currently track anywhere what files are part of base. -- Ticket URL: <https://trac.macports.org/ticket/37853#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#37853: RFE: "port provides" should return a different message when used on files provided by base --------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.2 Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by ryandesign@…): I've thought it would be neat if MacPorts base were encapsulated within the MacPorts port. Installing MacPorts for the first time would leave you with the MacPorts port already installed. "{{{port contents MacPorts}}}" would show everything installed by base, and "{{{port provides `which port`}}}" would then say "MacPorts". Upgrading MacPorts would then not be "{{{sudo port selfupdate}}}" but "{{{sudo port upgrade MacPorts}}}". And uninstalling MacPorts would be as easy as "{{{sudo port uninstall MacPorts}}}" though maybe we should have an extra safeguard on that (like ensuring that no other ports are installed). But currently that's not how it works, and currently users are not meant to install the MacPorts port; it's just used by us to prepare new releases of MacPorts for distribution. -- Ticket URL: <https://trac.macports.org/ticket/37853#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#37853: RFE: "port provides" should return a different message when used on files provided by base --------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.2 Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by egall@…): Replying to [comment:2 ryandesign@…]:
I've thought it would be neat if MacPorts base were encapsulated within the MacPorts port. Installing MacPorts for the first time would leave you with the MacPorts port already installed.
That was a potential GSOC project at one time, wasn't it? Link: https://trac.macports.org/wiki/SummerOfCode#self-management -- Ticket URL: <https://trac.macports.org/ticket/37853#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
#37853: RFE: "port provides" should return a different message when used on files provided by base --------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.2 Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by egall@…): I'd also like to add that this applies for files created by `port select`, too. -- Ticket URL: <https://trac.macports.org/ticket/37853#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS
#37853: RFE: "port provides" should return a different message when used on files provided by base --------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.2 Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by cal@…): Replying to [comment:5 egall@…]:
I'd also like to add that this applies for files created by `port select`, too.
I second that. Knowing which files are created by port select would also help in trace mode (because currently the symlinks created by port select can be used in trace mode, but this should be denied, because it can lead to non-reproducible builds). -- Ticket URL: <https://trac.macports.org/ticket/37853#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS
#37853: RFE: "port provides" should return a different message when used on files provided by base --------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.1.2 Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by egall@…): There is now a separate ticket for the `port select` part: #43996 (which makes sense, as it was kind of a separate issue in the first place) -- Ticket URL: <https://trac.macports.org/ticket/37853#comment:7> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts