Re: [gentoo-dev] Mozilla: Firebird-bin & Firebird-cvs

[Matthew Kennedy]

Jon Portnoy <avenj@g.o> writes:

> Policy is to avoid naming conflicts. :)
>
> There are indeed ebuilds that conflict. Those are bugs that there is
> currently no clean fix for. Committing _more_ conflicting ebuilds is
> definitely not okay.
>

Jon (and others), 

I'm not so sure.  I have app-emacs and app-xemacs and there are
*many* ebuilds which "conflict" in their naming, and this is
intentional.

For example, the "ilisp" package appears in both app-emacs and
app-xemacs.  So if I'm to avoid this naming "conflict" because
somemone typing "emerge ilisp" might get "app-xemacs/ilisp" instead
of "app-emacs/ilisp", then naturally I should prefix the ebuild names
with "emacs" and "xemacs", right?  So I'd end up with

   emerge emacs-ilisp
or
   emerge xemacs-ilisp

But wait!  Thats what categories are for -- ie. defining some
namespace. Thus there's no need, and this more or less backs up my
argument that the category name + package name forms a "fully resolved
and unique" symbol for emerge to act upon.

So the user should do:

   emerge app-emacs/ilisp
or
   emerge app-xemacs/ilisp

What of the case where the user is surprised by the "short form" case:

   emerge ilisp

...well this is where emerge should abort and report back to the user
something like this: "ERROR: Short form 'ilisp' matches
app-emacs/ilisp and app-xemacs/ilisp -- please use a fully qualified
name instead".  (Currently emerge emerges the first one it sees.)

I really think ambiguities should be resolved by using the category
name -- otherwise I can't see why we sort packages into categories
at all.

Matt   

-- 
Matthew Kennedy
Gentoo Linux Developer

--
gentoo-dev@g.o mailing list