From: Dave Nellans <dnellans@cs.utah.edu>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Mozilla: Firebird-bin & Firebird-cvs
Date: 28 May 2003 15:14:16 -0600 [thread overview]
Message-ID: <1054156454.2138.29.camel@malfus> (raw)
In-Reply-To: <87vfvuvl3x.fsf@killr.ath.cx>
[-- Attachment #1: Type: text/plain, Size: 2059 bytes --]
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?
perhaps its time we do
dave
On Wed, 2003-05-28 at 15:04, Matthew Kennedy wrote:
> Jon Portnoy <avenj@gentoo.org> 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
--
Dave Nellans
http://lucy.wox.org/~dnellans/
dnellans@cs.utah.edu
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-05-28 21:14 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 1:14 [gentoo-dev] Mozilla: Firebird-bin & Firebird-cvs Dhruba Bandopadhyay
2003-05-19 4:54 ` Russell Tennant
2003-05-19 5:38 ` Chris PeBenito
2003-05-19 9:56 ` Alastair 'liquidx' Tse
2003-05-19 11:01 ` Georgi Georgiev
2003-05-19 13:22 ` Alastair 'liquidx' Tse
2003-05-19 18:52 ` Martin Schlemmer
2003-05-19 6:40 ` Spundun Bhatt
2003-05-19 9:49 ` Christian Gut
2003-05-25 12:43 ` Christian Axelsson
2003-05-25 12:46 ` Dhruba Bandopadhyay
2003-05-25 12:56 ` Christian Axelsson
2003-05-25 13:16 ` Georgi Georgiev
2003-05-25 17:26 ` Zack Gilburd
2003-05-25 18:31 ` Jon Portnoy
2003-05-28 8:22 ` Matthew Kennedy
2003-05-28 8:47 ` Kumba
2003-05-28 9:06 ` Georgi Georgiev
2003-05-28 9:20 ` Kumba
2003-05-28 9:54 ` Michael Kohl
2003-05-28 14:06 ` Jon Portnoy
2003-05-28 18:13 ` George Shapovalov
2003-05-28 19:08 ` Jon Portnoy
2003-05-28 21:04 ` Matthew Kennedy
2003-05-28 21:14 ` Dave Nellans [this message]
2003-05-28 22:40 ` George Shapovalov
2003-05-29 3:22 ` Aron Griffis
2003-05-29 6:40 ` John Robinson
2003-05-29 10:17 ` Matt Tucker
2003-05-29 13:31 ` John Robinson
2003-05-29 14:00 ` Tavis Ormandy
2003-05-29 14:27 ` John Robinson
2003-05-30 7:03 ` Matthew Kennedy
2003-05-30 7:15 ` Georgi Georgiev
2003-05-30 10:52 ` Christian Axelsson
2003-05-30 15:23 ` Grant Goodyear
2003-06-15 11:28 ` Matthew Kennedy
2003-05-28 19:21 ` Jon Portnoy
2003-05-29 3:24 ` Aron Griffis
2003-05-30 6:45 ` Matthew Kennedy
2003-05-28 23:56 ` William F Pearson III
2003-05-28 9:08 ` Troy Dack
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1054156454.2138.29.camel@malfus \
--to=dnellans@cs.utah.edu \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox