Bug 22699 – emerge should fail when user tries to emerge an ambigously named package

• Status: RESOLVED FIXED
• Product: Portage Development

[Description Daniel Albuschat 2003-06-12 14:16:04 UTC]

there is app-xemacs/eterm and x11-terms/eterm what is confusing.

Reproducible: Always
Steps to Reproduce:
1. emerge -s eterm

[Comment 1 Seemant Kulleen (RETIRED) 2003-06-12 15:51:54 UTC]

matt, can we have the app-xemacs and app-emacs identical name stuff renamed?

the problem is, while I am not inherently or vehemently opposed to same-name packages, in cases especially like eterm and ispell and other common name things, the *expected default* changes with the inclusion of app-xemacs stuff -- simply because of portage's search order, which is alphabetical through categories, so invariably app-xemacs is one of the FIRST to be searched.

avenj tells me current policy prohibits nomenclature duplication.

[Comment 2 Matthew Kennedy (RETIRED) 2003-06-13 09:48:32 UTC]

seemant, i think this is one of those undecided things.  it was recently discussed quite well on gentoo-dev where i and others gave some good arguments for finally putting category names to use (officially -- 'cause they already work). iirc (i'd have to look it up), the resolution there was to simply have emerge print an error message like

   "emerge eterm" is ambigious, please specify one of the following 
   fully-qualified package names:

       x11-misc/eterm
       app-xemacs/eterm

This is also my preference.  Perhaps we should turn this bug into a portage feature request (to implement the above message)?  I'd soooooooo like to avoid screwing up the app-emacs and app-xemacs name-spaces, I'm willing to spend time creating the portage patch to implement it.

[Comment 3 ajs 2003-06-14 02:35:26 UTC]

Someone should close this bug, since the app-xemacs/eterm package appears to have been renamed app-xemacs/xemacs-eterm.

[Comment 4 Seemant Kulleen (RETIRED) 2003-06-14 02:52:53 UTC]

matt, would you submit a patch to nick for the portage feature?

[Comment 5 Matthew Kennedy (RETIRED) 2003-06-14 16:47:27 UTC]

seemant, okay

carpaski, any suggestions before I start to hack on it?

[Comment 6 Matthew Kennedy (RETIRED) 2003-06-15 04:25:13 UTC]

carpaski,

I created a patch for emerge at the following URL which will resolve this bug and possibly others. I've been testing it all night, and it works fine. its for portage version 2.0.48-r1

http://cvs.gentoo.org/~mkennedy/emerge-2.0.48-r1-shortname.patch

[Comment 7 Matthew Kennedy (RETIRED) 2003-09-01 21:24:37 UTC]

corrected url 

http://dev.gentoo.org/~mkennedy/emerge-2.0.48-r1-shortname.patch

[Comment 8 Nicholas Jones (RETIRED) 2003-12-28 22:17:33 UTC]

*** Bug 13903 has been marked as a duplicate of this bug. ***

[Comment 9 Masatomo Nakano (RETIRED) 2003-12-29 01:06:00 UTC]

I fixed that in cvs.
Thanks

[Comment 10 Marius Mauch (RETIRED) 2004-01-12 01:24:24 UTC]

*** Bug 28347 has been marked as a duplicate of this bug. ***

[Comment 11 Marius Mauch (RETIRED) 2004-02-08 17:55:23 UTC]

supposed to be fixed in 2.0.50 which is stable now. If this bug is not fixed please reopen.