Opened 6 years ago
Last modified 2 years ago
#42207 assigned enhancement
uninstalling macports could be easier
| Reported by: | dave@… | Owned by: | neverpanic (Clemens Lang) |
|---|---|---|---|
| Priority: | Normal | Milestone: | MacPorts 2.7.0 |
| Component: | base | Version: | |
| Keywords: | Cc: | ryandesign (Ryan Schmidt), umeshksingla (Umesh Singla) | |
| Port: |
Description
Instead of getting the user to know about and to follow the directions here, MacPorts could do all of that itself when the user issues a port command, such as
port uninstall macports
or
port selfuninstall
Change History (6)
comment:1 Changed 6 years ago by mf2k (Frank Schima)
| Component: | ports → base |
|---|---|
| Type: | defect → enhancement |
| Version: | 2.2.1 |
comment:2 Changed 6 years ago by ryandesign (Ryan Schmidt)
| Cc: | ryandesign@… added |
|---|
comment:3 Changed 2 years ago by neverpanic (Clemens Lang)
| Milestone: | → MacPorts 2.6.0 |
|---|---|
| Owner: | changed from macports-tickets@… to neverpanic |
| Status: | new → assigned |
We can ship the command from the guide in a shell script, e.g. in $prefix/libexec/macports/uninstall to simplify uninstalling.
This would also have the advantage of being able to remove the correct $applications_dir for the installation that is being removed.
comment:4 Changed 2 years ago by umeshksingla (Umesh Singla)
| Cc: | umeshksingla added |
|---|
comment:6 Changed 2 years ago by mojca (Mojca Miklavec)
| Milestone: | MacPorts 2.6.0 → MacPorts 2.7.0 |
|---|
Note: See
TracTickets for help on using
tickets.

Uninstalling MacPorts could be easier. On the other hand, how easy do we really want it to be to uninstall everything, which is a drastic and irreversible step and also something that won't be done regularly?
And a couple problems come to mind with this proposal:
portanything and need to uninstall manually.We could offer a separate shell script to uninstall.
The proposed self-management feature may address this concern.