| 1 |
I have never seen a good reason why a package *shoulnt* be in the world |
| 2 |
file. Especially dependencies. I am continually getting surprised by |
| 3 |
emerge -s showing new versions of packages that emerge -u and sometimes |
| 4 |
emerge -uD do not see. Not good. |
| 5 |
|
| 6 |
depclean is unclean = system breaker. |
| 7 |
|
| 8 |
It has its uses, but when it goes wrong ... |
| 9 |
|
| 10 |
BillK |
| 11 |
|
| 12 |
On Thu, 2005-10-13 at 11:16 +0200, Holly Bostick wrote: |
| 13 |
> Jorge Almeida schreef: |
| 14 |
> > I don't do much emerge world, I usually just "-p"-it and then emerge |
| 15 |
> > each package, that's why I didn't think of that. |
| 16 |
> |
| 17 |
> That seems like a waste of effort -- and 'corrupts' your world file, as |
| 18 |
> well, since everything you emerge explicitly will be entered into your |
| 19 |
> world file, and that will then include dependencies, which should by |
| 20 |
> rights *not* be in your world file, nothing said about dependencies of |
| 21 |
> dependencies, also known as 'deep dependencies'. |
| 22 |
> |
| 23 |
> You're really making a mess doing that; you'll screw up emerge |
| 24 |
> --depclean, for one thing, since I have no idea what it would do if a |
| 25 |
> dependency of an uninstalled package in your world file (which would |
| 26 |
> normally make the package a valid target for depclean) is also in your |
| 27 |
> world file, given that dependencies are not meant to be in your world |
| 28 |
> file (thereby invalidating the now-useless package as a depclean target): |
| 29 |
> |
| 30 |
|
| 31 |
-- |
| 32 |
gentoo-user@g.o mailing list |
Archives