Opened 14 years ago
Last modified 14 years ago
#26853 new enhancement
MacPorts should say why it is (re)installing a dependency
| Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | base | Version: | 1.9.1 |
| Keywords: | Cc: | ||
| Port: |
Description
There are now several reasons why MacPorts might build or rebuild a dependency:
- it is not installed
- it is outdated
- it has the wrong variants
- it has the wrong architectures
- perhaps other reasons?
Several times now I have noticed MacPorts rebuilding a dependency though as far as I can tell it is already installed, with the right version, with the right variants, with the right architectures. It would be nice to know why MacPorts thinks it needs to be rebuilt.
Note: See
TracTickets for help on using
tickets.
I should add that it's usually a PEBKAC: once MacPorts updated python26 and I didn't understand why, until it was done and I saw that it now had a different set of default variants. Another time a dependency was unexpectedly built that I thought I had already installed, but it turned out I had installed it in a different MacPorts prefix. Still, if MacPorts had told me why it was doing what it was doing, it might've been clearer to me what was going on.