public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Francesco Talamona <francesco.talamona@know.eu>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: autodepclean script (was "how to remove HAL")
Date: Sat, 21 Aug 2010 12:07:40 +0200	[thread overview]
Message-ID: <201008211207.40833.francesco.talamona@know.eu> (raw)
In-Reply-To: <20100819030541.GA7423@waltdnes.org>

On Thursday 19 August 2010, Walter Dnes wrote:
> On Tue, Aug 17, 2010 at 09:49:22PM +0200, Enrico Weigelt wrote
> 
> > I've just experimented a bit with that and it turned out that
> > --depclean doesn't clean up the buildtime-only deps. But if I
> > remove one of them (eg. cabextract), they don't get pulled in again
> > (that's indicating the depending ebuilds are written properly).
> 
>   This reminds me of a script I've been working on to remove
> unnecessary cruft.  Everything that follows is run as root, because
> it runs "emerge".  The attached script "autodepclean" parses the
> output from "emerge --pretend --depclean" and generates a script
> "cleanscript" that you can run to clean up your system.  This should
> handle your situation, but it's also a general solution to the
> entire class of problems of cleaning up when you remove all programs
> or USE flags that pull in a lib.  It is not restricted to just HAL
> 
>   Warning, this script is beta.  Use with care.  It will remove
> gentoo-sources versions higher than your current kernel.  This is
> technically correct for removing unused ebuilds.  But it may not be
> what you want.

I'm unclear about the aim of your script, what does different from 
"emerge -a --depclean" followed by "revdep-rebuild -- -a"?

Ciao
	Francesco
-- 
Linux Version 2.6.35-gentoo-r1, Compiled #1 SMP PREEMPT Wed Aug 11 
07:11:30 CEST 2010
Two 1GHz AMD Athlon 64 Processors, 4GB RAM, 4021.84 Bogomips Total
aemaeth



  reply	other threads:[~2010-08-21 10:08 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-28  2:44 [gentoo-user] how to remove HAL sam new
2010-07-28  5:01 ` Alan McKinnon
2010-07-28 13:34   ` sam new
2010-07-28 15:08     ` Alan McKinnon
2010-07-29  2:26       ` sam new
2010-07-29  6:39         ` Alan McKinnon
2010-07-29  8:07           ` sam new
2010-07-28 16:46     ` Volker Armin Hemmann
2010-07-28  8:05 ` Neil Bothwick
2010-08-17 19:49   ` Enrico Weigelt
2010-08-18 13:22     ` Mike Edenfield
2010-08-19  3:05     ` [gentoo-user] autodepclean script (was "how to remove HAL") Walter Dnes
2010-08-21 10:07       ` Francesco Talamona [this message]
2010-08-21 23:32         ` [gentoo-user] " Walter Dnes
2010-08-22  9:45           ` Francesco Talamona
2010-08-19  9:57     ` [gentoo-user] how to remove HAL Neil Bothwick
2010-07-28 16:31 ` [gentoo-user] " Nikos Chantziaras
2010-07-28 17:23   ` Neil Bothwick
2010-07-28 18:50     ` Nikos Chantziaras
2010-07-28 20:54       ` Andrey Vul
2010-07-28 21:08         ` Nikos Chantziaras
2010-07-28 21:22           ` Alan McKinnon
2010-07-29  0:31           ` [gentoo-user] " Andrey Vul
2010-07-29  0:38             ` [gentoo-user] " Nikos Chantziaras
2010-07-29  0:44               ` Nikos Chantziaras
2010-07-29  0:33           ` [gentoo-user] " Andrey Vul
2010-07-29  2:24       ` [gentoo-user] " sam new

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201008211207.40833.francesco.talamona@know.eu \
    --to=francesco.talamona@know.eu \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox