Emerging app-emacs/color-theme requires emacs 21.4. I'm already using another build, 22.1.1. Shouldn't the dependancy already be met? Reproducible: Always Steps to Reproduce: 1. Have installed a version of Emacs besides the default stable build 2. Emerge color-theme 3. Portage wants to install emacs 21.4-r12 Expected Results: color-theme's dependency on emacs should already be met.
Please post the output of "emerge -pv virtual/emacs" and the contents of your package.unmask file.
I missed adding NEED_EMACS=version_number to the elisp.eclass. After fixing that, the virtual emacs22 was emerged fine. I'm not sure if it would help other people to have a virtual emacs auto emerged depending on what version of emacs the person has installed. If someone has multiple ones, then at least have one virtual.
(In reply to comment #2) > I missed adding NEED_EMACS=version_number to the elisp.eclass. After fixing > that, the virtual emacs22 was emerged fine. I'm not sure if it would help other > people to have a virtual emacs auto emerged depending on what version of emacs > the person has installed. If someone has multiple ones, then at least have one > virtual. I think your problem is that you have no virtual/emacs installed. If you just emerged emacs-22 (or emacs-cvs), you still need a virtual/emacs as all app-emacs packages depend on that. Put virtual/emacs-22 in your package.keywords and try again. So please provide the information, Ulrich asked for in comment #1
I'd rather guess virtual/emacs-21 is installed (it's marked stable on most arches), but virtual/emacs-22 cannot be pulled in, because it's marked ~arch only: (In reply to comment #0) > 1. Have installed a version of Emacs besides the default stable build Adding =virtual/emacs-22 to package.unmask (or even package.keywords) would fix the problem in this case. But that's a guess only; so far the Reporter has not even revealed which architecture he's using.
My package.unmask has no contents of emacs but I have added "~virtual/emacs-22" to package.keywords. After emerging virtual emacs22, color-theme emerged without needing emacs21. It's fixed now and I understand that since virtual22 is masked, it won't automatically be installed with emacs22.
Good. Please note that virtual/emacs must always be unmasked/keyworded in the same way as app-editors/emacs{,-cvs}, since the app-emacs packages will pull the virtual as dependency. (This is a bit hidden, in elisp.eclass.) RESOLVED NOTABUG.
