Opened 18 years ago
Closed 18 years ago
#10378 closed defect (invalid)
port upgrade tries to install libtool even though libtool-devel is present
| Reported by: | jaris@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | base | Version: | 1.2 |
| Keywords: | Cc: | markd@… | |
| Port: |
Description
"Error: Activating libtool 1.5.22_0 failed: Image error: /opt/local/bin/glibtool is being used by the active libtool-devel port. Please deactivate this port first, or use the -f flag to force the activation."
I had to use the -n flag when upgrading to avoid this. Haven't checked if it exists, but wouldn't it be possible to provide several mutually exclusive dependencies to fix this?
Change History (3)
comment:1 Changed 18 years ago by danielluke (Daniel J. Luke)
comment:2 Changed 18 years ago by jaris@…
(In reply to comment #1)
Not really, with the current dependency engine.
Well, having each port provide those mutually exclusive dependencies would be rather unmanageable.
Rather, if there was a way for the port to declare itself equivalent with another port for the purpose of dependencies. Or the original dependency has the names of equivalent ports if that makes lookup easier.
comment:3 Changed 18 years ago by markd@…
| Cc: | markd@… added |
|---|---|
| Resolution: | → invalid |
| Status: | new → closed |
This isn't a defect; this would be an enhancement if pursued. I'm going to close this, but if you'd like it to be an RFE you may open a ticket and flag it as 'enhancement' and describe the general feature to base you'd like to request.
(In reply to comment #0)
Not really, with the current dependency engine.