Date: Tue, 3 Mar 2009 08:36:17 -0900 From: Mel <fbsd.questions@rachie.is-a-geek.net> To: freebsd-questions@freebsd.org Cc: Robert Huff <roberthuff@rcn.com>, lacalling <lacalling@gmail.com> Subject: Re: A problem about pkg_deinstall Message-ID: <200903030836.17672.fbsd.questions@rachie.is-a-geek.net> In-Reply-To: <18858.39797.40001.573615@jerusalem.litteratus.org> References: <de8d0ce00902282255x75100d00ha05a13c555e9ff9@mail.gmail.com> <200902282247.22739.fbsd.questions@rachie.is-a-geek.net> <18858.39797.40001.573615@jerusalem.litteratus.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday 01 March 2009 05:28:05 Robert Huff wrote:
> Mel writes:
> > Aside what Michael pointed out, ports-mgmt/pkg_cutleaves is much
> > easier for this task. It will only delete leaves, so if b is
> > still needed by X, it will not come up on the next iteration. And
> > you get to see the short description of the package, so may
> > decide to keep it anyway...
>
> I'd like to suggest a better solution is not auto-deleting in
> either direction. Even if the code were perfect - of which there is
> no evidence - the people are not, Unless you're (generic "you")
> planning to wipe out something huge (e.g. X11, or Gnome/KDE) and
> know _exactly_ what you're doing ... it's like hanging a "Kick me!"
> sign around your neck.
pkg_cutleaves is interactive by default. Asks confirmation for each port, then
only deletes at the end of the run. Unless you explicitedly tell it to be not
interactive...
Really should check it out. My only beef with it is that it writes "kept"
packages as package names, rather then origin, so keeping autoconf-2.56 will
result in all autoconf packages to be kept next run.
--
Mel
Problem with today's modular software: they start with the modules
and never get to the software part.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200903030836.17672.fbsd.questions>