From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4215 invoked by uid 1002); 11 Feb 2003 17:03:02 -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 31720 invoked from network); 11 Feb 2003 17:03:02 -0000 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Date: Tue, 11 Feb 2003 08:54:14 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: RE: [gentoo-dev] Portage as a dependency Thread-Index: AcLOy8He18ODm6hhSxa2eX8szKdyRQDIjRTAAAAKSBA= From: "Sean P. Kane" To: Subject: RE: [gentoo-dev] Portage as a dependency X-Archives-Salt: d8e21725-7c74-45b9-ba30-5a694d2f5409 X-Archives-Hash: 64340921d93f6f60ca5740bcfcab97e5 This is a very new feature of portage, it didn't do this until very recently and it isn't really helpful if you are only emerging one pacakge and it is DEPENDANT on a particular version of Portage, yet doesn't require that version in it's ebuild. Sean -----Original Message----- From: Alain Penders [mailto:alain@gentoo.org]=20 Sent: Friday, February 07, 2003 09:07 To: gentoo-dev@gentoo.org Subject: Re: [gentoo-dev] Portage as a dependency I would hope that people rsync before installing new packages -- saves having=20 to install them twice. After the rsync, if you run emerge -up world, you'll get a specific message in the package list about a new portage being=20 available. Isn't this and the general knowledge that Gentoo hinges on portage enough for people to update portage before emerging other packages? Alain On Fri, Feb 07, 2003 at 08:49:38AM -0800, Sean P. Kane wrote: > An example of a package is x11-base/xfree-4.2.1-r2 which requries a > version of Portage that doesn't experience BUG 13013=20 > http://bugs.gentoo.org/show_bug.cgi?id=3D13013. If people know this it = > would be very helpful to either makrk it as a dependency, which may=20 > actually be too difficult for package mantainers to keep updated, or=20 > allow Portage to have an auto-update feature that will always update=20 > Portage before doing other emerges. >=20 > Sean >=20 >=20 > -----Original Message----- > From: Dylan Carlson [mailto:absinthe@pobox.com] > Sent: Thursday, February 06, 2003 19:30 > To: Sean P. Kane; gentoo-dev@gentoo.org > Subject: Re: [gentoo-dev] Portage as a dependency >=20 >=20 > On Thursday 06 February 2003 06:17 pm, Sean P. Kane wrote: > > I reported a bug earlier today that turned out to be caused by a=20 > > slightly older version of Portage. Shouldn't we consider having=20 > > portage or the ebuilds handle this type of situation better, by=20 > > either >=20 > > having the ebuilds have a particular version of portage as a=20 > > dependency or making portage always check for a newer stable version > > of portage whenever it does an emerge and then upgrading to that=20 > > first. >=20 > RDEPEND=3D">=3Dsys-apps/portage-2.0.47", as an example, is one way an > ebuild >=20 > can do it. =20 >=20 > Furthermore, Portage should be backward compatible with ebuilds > written for earlier versions. DEPEND/RDEPEND should be all that is=20 > necessary in situations where an ebuild depends on a newer, masked=20 > version of Portage >=20 > -- if that is in fact necessary. >=20 > Cheers, > Dylan Carlson >=20 > -- > gentoo-dev@gentoo.org mailing list >=20 >=20 > -- > gentoo-dev@gentoo.org mailing list >=20 -- gentoo-dev@gentoo.org mailing list -- gentoo-dev@gentoo.org mailing list