From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25682 invoked by uid 1002); 16 Apr 2003 00:35:11 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 12110 invoked from network); 16 Apr 2003 00:35:11 -0000 From: Peter Ruskin Organization: Retired To: gentoo-dev@gentoo.org Date: Wed, 16 Apr 2003 01:35:03 +0100 User-Agent: KMail/1.5.1 References: <1050450162.18807.6.camel@malfus> <200304151711.23346.george@gentoo.org> <1050454731.18808.32.camel@malfus> In-Reply-To: <1050454731.18808.32.camel@malfus> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200304160135.03508.aoyu93@dsl.pipex.com> Subject: Re: [gentoo-dev] ebuild naming policy X-Archives-Salt: f4ac065f-12cd-4702-bd4f-e17c891e5f13 X-Archives-Hash: a1d637f0d43a8d4bb52ccddfaed1f605 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 /.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