public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Ruskin <aoyu93@dsl.pipex.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] ebuild naming policy
Date: Wed, 16 Apr 2003 01:35:03 +0100	[thread overview]
Message-ID: <200304160135.03508.aoyu93@dsl.pipex.com> (raw)
In-Reply-To: <1050454731.18808.32.camel@malfus>

On Wednesday 16 Apr 2003 01:58, Dave Nellans wrote:
> The question then remains is how to determine which package is the
> "default" to be installed if you use only the ebuild name.  I haven't
> poked in the code to see how portage is doing it now, but can see three
> possible options.  One being alphabetical by category, two being first
> come first serve, or three allowing the "most commonly installed" of
> the options defined by whomever is maintaining the package(s).  The
> only downside is that portage/ebuilds will need yet another thing added
> to it similar to SLOTS to help support this =/

Or perhaps better, emerge should fail and print a message like:
"There is more than one package with that name.  Please use
'emerge <category>/<package>.ebuild' for the required package.'"

Peter
-- 
Gentoo-1.4.2.8 Stable. KDE: 3.1.1a Qt: 3.1.2
AMD Athlon(tm) XP 2200+ 768MB.	Kernel: 2.4.20-xfs-r2.	GCC 3.2.2


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-04-16  0:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-15 23:42 [gentoo-dev] ebuild naming policy Dave Nellans
2003-04-15 23:16 ` Jon Portnoy
2003-04-16  0:03   ` Dave Nellans
2003-04-15 23:43     ` Fred Van Andel
2003-04-16  0:11     ` George Shapovalov
2003-04-16  0:58       ` Dave Nellans
2003-04-16  0:35         ` Peter Ruskin [this message]
2003-04-16  1:39           ` Jeff Rose
2003-04-16  2:43             ` George Shapovalov
2003-04-16  8:15               ` Paul de Vrieze
2003-04-16 13:30                 ` Chris Bainbridge
2003-04-15 23:20 ` Chris PeBenito

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=200304160135.03508.aoyu93@dsl.pipex.com \
    --to=aoyu93@dsl.pipex.com \
    --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