| 1 |
On Sunday 22 August 2010, Walter Dnes wrote: |
| 2 |
> On Sat, Aug 21, 2010 at 12:07:40PM +0200, Francesco Talamona wrote |
| 3 |
> |
| 4 |
> > I'm unclear about the aim of your script, what does different from |
| 5 |
> > "emerge -a --depclean" followed by "revdep-rebuild -- -a"? |
| 6 |
> |
| 7 |
> The autodepclean script automatically generates a list of of target |
| 8 |
> ebuuilds to clean out (i.e. "cleanscript"). This gives you the |
| 9 |
> opportunity to review it and delete items from the list before going |
| 10 |
> ahead. Does "emerge -a --depclean" allow you to skip individual |
| 11 |
> items? |
| 12 |
|
| 13 |
Ah ok, now i see the point. Usually I prefer to stop depclean (answering |
| 14 |
no) and specify the exceptions with emerge --noreplace. |
| 15 |
|
| 16 |
This is because the exclusion of some packages from depclean can affect |
| 17 |
the following result of it. |
| 18 |
|
| 19 |
If you install a package having many dependencies, with emerge --oneshot |
| 20 |
and then run emerge --depclean you'll see that is easier to run two |
| 21 |
times depclean than edit the generated list :) |
| 22 |
|
| 23 |
Cheers |
| 24 |
Francesco |
| 25 |
-- |
| 26 |
Linux Version 2.6.35-gentoo-r1, Compiled #1 SMP PREEMPT Wed Aug 11 |
| 27 |
07:11:30 CEST 2010 |
| 28 |
Two 2.9GHz AMD Athlon 64 Processors, 4GB RAM, 11657 Bogomips Total |
| 29 |
aemaeth |
Archives