| 1 |
On Tue, 13 May 2008 11:46:26 -0500, reader@×××××××.com wrote: |
| 2 |
|
| 3 |
> > Another possibility is that ypou merged them with the --oneshot |
| 4 |
> > option, or that they were pulled in as a dependency of a package you |
| 5 |
> > no longer have (or has been updated to a version that is no longer |
| 6 |
> > dependent on them). What does "emerge --depclean -p" show? |
| 7 |
> |
| 8 |
> Along with dire warnings about ruining your system it lists 80 pkgs to |
| 9 |
> be removed. Some are also on the eix-test-obsolete list of 14. |
| 10 |
> |
| 11 |
> I suspect I had better not allow it to actually remove these pkgs. |
| 12 |
|
| 13 |
I think you should, as long as nothing system-critical is listed, and |
| 14 |
emerge shouts loudly about removing those. |
| 15 |
|
| 16 |
> For example, one of the listed pkgs is: |
| 17 |
> |
| 18 |
> gnome-base/libgnomeui |
| 19 |
> |
| 20 |
> which equery says `firefox' and `etherape' depend on. |
| 21 |
|
| 22 |
equery depends is unreliable as it doesn't take proper account of USE |
| 23 |
dependencies. What's the worst that can happen if you unmerge libgnomeui? |
| 24 |
Probably that you can't start a GNOME desktop until it is re-emerged. As |
| 25 |
long as you don't unmerge anything fro system and you run a deep world |
| 26 |
update after a depclean, preferably followed by a revdep-rebuild, you |
| 27 |
should be OK. |
| 28 |
|
| 29 |
However, if this advice does break your computer, feel free to keep the |
| 30 |
pieces :) |
| 31 |
|
| 32 |
|
| 33 |
-- |
| 34 |
Neil Bothwick |
| 35 |
|
| 36 |
ASSISTANT MANAGER: Feminine form of the word manager (q.v.). |
Archives