| 1 |
On Fri, Sep 2, 2011 at 12:17 PM, Mark Knecht <markknecht@×××××.com> wrote: |
| 2 |
|
| 3 |
> On Fri, Sep 2, 2011 at 12:06 PM, Sebastian Beßler |
| 4 |
> <sebastian@××××××××××××.de> wrote: |
| 5 |
> > Am 02.09.2011 18:09, schrieb Mark Knecht: |
| 6 |
> > |
| 7 |
> >> I believe you can trust it, but why use --depclean instead of just -C? |
| 8 |
> > |
| 9 |
> > If you unmerge with -C you have to be sure that nothing needs it as a |
| 10 |
> > dependency. Using --depclean helps because it checks that and only |
| 11 |
> > unmerges if nothing needs it as a dependency anymore. |
| 12 |
> > |
| 13 |
> > Greetings |
| 14 |
> > |
| 15 |
> > Sebastian |
| 16 |
> |
| 17 |
> Fair enough. Thanks. Presumably the use of --depclean doesn't work |
| 18 |
> until you're clear with emerge -DuN @world? |
| 19 |
> |
| 20 |
> I've used this stuff so long I've not learned many of the newer tricks |
| 21 |
> I think. Good stuff. |
| 22 |
> |
| 23 |
> Cheers, |
| 24 |
> Mark |
| 25 |
> |
| 26 |
> |
| 27 |
It depends on the package you're trying to remove, but often in my |
| 28 |
experience when using depclean on a single package it works fine without |
| 29 |
updating world. |
| 30 |
Also, -c is an alias for --depclean. |
Archives