GimmeFuel wrote:

> # emerge -up world
> [ebuild U ] sys-apps/portage-2.0.49-r21 [2.0.49-r20]
> [ebuild UD] x11-libs/openmotif-2.1.30-r3 [2.2.2-r1]
> [ebuild N ] app-editors/xemacs-21.4.12
> [ebuild U ] sys-apps/groff-1.18.1-r4 [1.18.1-r3]
> [ebuild U ] sys-devel/autoconf-2.58 [2.57-r1]
> [ebuild U ] x11-wm/fluxbox-0.9.7-r1 [0.1.14-r20
>
> Why does xemacs show up? I had it emerged but then I unmerged it; it's
> not in world anymore. 'emerge xemacs && emerge -C xemacs' didn't do
> anything. I've also used emerge -upv world to see what USE flags are
> active, but no combination of USE flags I've tried will make xemacs go
> away. I asked in #gentoo, all they could come up with was that
> something depends on xemacs, but what? I'm almost positive I haven't
> emerged anything that needs on it. Is there any way to tell why
> portage thinks I need xemacs?

Try running emerge with '-d'. The output will be quite verbose, so you
might want to pipe it to 'less'. Look for anything mentioning xemacs,
and read back a little. That'll give you a clue as to why emerge thinks
xemacs is needed. It's the same method I used to figure out why tetex
kept being recursively upgraded and downgraded.

--
PeKaJe

"Humor is a drug which it's the fashion to abuse."
-- William Gilbert