From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-dev-return-3371-arch-gentoo-dev=gentoo.org@gentoo.org>
Received: (qmail 25866 invoked by uid 1002); 28 May 2003 21:14:42 -0000
Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm
Precedence: bulk
List-Post: <mailto:gentoo-dev@gentoo.org>
List-Help: <mailto:gentoo-dev-help@gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev-unsubscribe@gentoo.org>
List-Subscribe: <mailto:gentoo-dev-subscribe@gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@gentoo.org
Received: (qmail 22957 invoked from network); 28 May 2003 21:14:42 -0000
From: Dave Nellans <dnellans@cs.utah.edu>
Reply-To: dnellans@cs.utah.edu
Cc: gentoo-dev@gentoo.org
In-Reply-To: <87vfvuvl3x.fsf@killr.ath.cx>
References: <1053306873.1543.8.camel@wolf.codewordt.co.uk>
	 <20030528090637.GB13935%chutz@gg3.net>
	 <20030528140638.GA12271@cerberus.oppresses.us>
	 <200305281113.59132.george@gentoo.org>
	 <20030528190854.GA16794@cerberus.oppresses.us>
	 <87vfvuvl3x.fsf@killr.ath.cx>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-09n4lCWrouwrBjkAvQvq"
Organization: U of Utah
Message-Id: <1054156454.2138.29.camel@malfus>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.4- 
Date: 28 May 2003 15:14:16 -0600
Subject: Re: [gentoo-dev] Mozilla: Firebird-bin & Firebird-cvs
X-Archives-Salt: 4ce00077-53a4-4086-baca-24324a16d7e4
X-Archives-Hash: bc16d47261a4a015fb17e311cdc9db9e

--=-09n4lCWrouwrBjkAvQvq
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

this is something we discussed about a month ago and never developed an
official policy for then did we? george can you comment on this?=20
perhaps its time we do

dave

On Wed, 2003-05-28 at 15:04, Matthew Kennedy wrote:
> Jon Portnoy <avenj@gentoo.org> writes:
>=20
> > Policy is to avoid naming conflicts. :)
> >
> > There are indeed ebuilds that conflict. Those are bugs that there is=20
> > currently no clean fix for. Committing _more_ conflicting ebuilds is=20
> > definitely not okay.
> >
>=20
> Jon (and others),=20
>=20
> 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.
>=20
> 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
>=20
>    emerge emacs-ilisp
> or
>    emerge xemacs-ilisp
>=20
> 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.
>=20
> So the user should do:
>=20
>    emerge app-emacs/ilisp
> or
>    emerge app-xemacs/ilisp
>=20
> What of the case where the user is surprised by the "short form" case:
>=20
>    emerge ilisp
>=20
> ...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.)
>=20
> 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.
>=20
> Matt  =20
--=20
Dave Nellans
http://lucy.wox.org/~dnellans/
dnellans@cs.utah.edu

--=-09n4lCWrouwrBjkAvQvq
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQA+1SamdtkLPRim+bkRAvSlAKCSF1h3VIyJAqIf8CAudwFjYRpHFACfYyMp
8CzjP4YSArosUvBsEjN6quc=
=Kj5v
-----END PGP SIGNATURE-----

--=-09n4lCWrouwrBjkAvQvq--