Holly Bostick wrote: >Anthony E. Caudel schreef: > > >>Ah, the "profile" threw me. I was thinking profiles and not the emerge >>system I had done originally. >> >>I use nano so I guess I can unmerge it safely. But I'm still at a loss >>why the warning should come up. Emacs is not listed in base/packages >>nor linux-default/packages nor x86/packages and finally not in >>2005.0/packages. I am correct in thinking these constitute "system," >>right. It also is not in my make.conf nor is it pulled in by any other >>package (emerge info does not list it as a USE flag). >> >>Tony >> >> > >Did you check /etc/portage/package.use? Afaik, USE flags listed there >are not listed by emerge info, and that's the only other thing I can >think of; emacs must have been installed as a explicit dependency of a >particular system package (or sub-dependency of such). > > Nope, nothing relevant in package.use. Oh well, unmerged it and revdep-rebuild didn't complain so THWI.
>You could also explicitly set "-emacs" in /etc/make.conf and see what >changes in an emerge -uaDNtv world (or system), which would not only >tell you why emacs is involved in this (I, for example, don't have it at >all, and I suppose our systems are basically similar), as well as >orphaning the dependency, so you could clean it out safely with a >depclean (or normally, without the warning). > >HTH, >Holly > > -- Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin -- [EMAIL PROTECTED] mailing list
