From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7681 invoked by uid 1002); 7 Feb 2003 16:57:42 -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 16704 invoked from network); 7 Feb 2003 16:57:42 -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: Fri, 7 Feb 2003 08:49:38 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [gentoo-dev] Portage as a dependency Thread-Index: AcLOWeYJTS7npLG+RJOnl+pwGCBuMwAbmirg From: "Sean P. Kane" To: Subject: RE: [gentoo-dev] Portage as a dependency X-Archives-Salt: 8eedeff9-8038-43ad-a38f-1fc873cf8635 X-Archives-Hash: 5df2c1cc33c2c10289bd80e0e02c7f1e 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 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 actually be too difficult for package mantainers to keep updated, or allow Portage to have an auto-update feature that will always update Portage before doing other emerges. Sean -----Original Message----- From: Dylan Carlson [mailto:absinthe@pobox.com]=20 Sent: Thursday, February 06, 2003 19:30 To: Sean P. Kane; gentoo-dev@gentoo.org Subject: Re: [gentoo-dev] Portage as a dependency 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 either > having the ebuilds have a particular version of portage as a=20 > dependency or making portage always check for a newer stable version=20 > of portage whenever it does an emerge and then upgrading to that=20 > first. RDEPEND=3D">=3Dsys-apps/portage-2.0.47", as an example, is one way an = ebuild can do it. =20 Furthermore, Portage should be backward compatible with ebuilds written for=20 earlier versions. DEPEND/RDEPEND should be all that is necessary in=20 situations where an ebuild depends on a newer, masked version of Portage -- if that is in fact necessary. Cheers, Dylan Carlson -- gentoo-dev@gentoo.org mailing list -- gentoo-dev@gentoo.org mailing list