Atlas compiling causes havoc

[Ryan Schmidt]

On May 20, 2012, at 01:03, Jasper Frumau wrote:

> My question is. Do you think I can dump Atlas and all its dependencies?

If you have no recollection of needing or wanting atlas (or another port), feel free to "sudo port uninstall" it. If atlas is a dependency of something you've installed, MacPorts will tell you so, and will prevent you from uninstalling it. So you can feel free to "sudo port uninstall" things you don't think you need, secure in the knowledge that it will not break anything.


You may also want to use the "leaves" feature. "Leaves" are the ports MacPorts installed as dependencies but that you didn't specifically ask for. The opposite of "leaves" are the "requested" ports—the ones you actually "sudo port install"ed by name.


You can use:

port installed requested

to see the ports MacPorts thinks you actually want. If there are any listed that you don't actually want (maybe you "sudo port install"ed something while troubleshooting a build problem) you can use:

sudo port unsetrequested foo

to mark the port "foo" as not something you care to have installed.


Similarly you can use:

port installed leaves

to see the ports that are installed that aren't used by any other port that MacPorts thinks you don't care about. If there are any in the list that you do care about, you can use:

sudo port setrequested foo

to mark a port "foo" as something that you want to keep arouund.


Finally, you can use:

sudo port uninstall leaves

to uninstall all the ports you don't care about that aren't required by anything else.