Opened 12 years ago
Last modified 10 years ago
#37853 new enhancement
RFE: "port provides" should return a different message when used on files provided by base
| Reported by: | cooljeanius (Eric Gallager) | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | base | Version: | 2.1.2 |
| Keywords: | Cc: | larryv (Lawrence Velázquez) | |
| Port: |
Description
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?
Change History (7)
comment:1 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
comment:2 follow-up: 3 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
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.
comment:3 Changed 12 years ago by cooljeanius (Eric Gallager)
Replying to 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
comment:5 follow-up: 6 Changed 12 years ago by cooljeanius (Eric Gallager)
I'd also like to add that this applies for files created by port select, too.
comment:6 Changed 12 years ago by neverpanic (Clemens Lang)
Replying to 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).
comment:7 Changed 10 years ago by cooljeanius (Eric Gallager)
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)
I don't think we currently track anywhere what files are part of base.