"sudo port upgrade outdated" fills HDD

Sam Kuper sam.kuper at uclmail.net
Wed Feb 17 20:53:34 PST 2010

On 18 February 2010 02:44, Ryan Schmidt <ryandesign at macports.org> wrote:

> On Feb 17, 2010, at 20:29, Sam Kuper wrote: [...]
> > I guess a better solution would be to somehow have MacPorts or
> port_cutleaves be aware of which ports had had their installation requested
> by a user, and to have port_cutleaves have the option only to list those
> leaves and to automatically uninstall them and everything below on the
> dependency branch, if requested.
> Yeah. Since MacPorts doesn't remember that at present, port_cutleaves has a
> handy feature where you can record this list of ports yourself, as regular
> expressions, in a text file called .port_leaves.exclude in your home
> directory. A few lines from my .port_leaves.exclude file:
> ^graphviz
> ^grep
> ^gv
> ^gzip
> ^ImageMagick
> ^q
> Note that I begin each line with "^" (regular expression syntax for anchor
> to beginning of line) and end each with a space (because the regular
> expression will end up matching something similar to the output of "port
> installed", which includes not only the port name but also the version and
> variants, separated from the port name by a space). I end each line with a
> space, for example "^q ", because I want to keep the port "q" but don't want
> to also keep every other port whose name begins with "q". For some ports,
> though, I don't end with a space: e.g. I use "^graphviz" because I want to
> keep all graphviz-related ports because I'm the maintainer of all of them.

Cunning! I read man port_exclude but didn't understand the part about the
exclude file, so thanks for this explanation, which was much more

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20100218/0551ca10/attachment.html>

More information about the macports-users mailing list