Gentoo Archives: gentoo-dev

From: Alain Penders <alain@g.o>
To: gentoo-dev@g.o
Subject: Re: [gentoo-dev] Portage as a dependency
Date: Fri, 07 Feb 2003 17:14:53
Message-Id: 20030207170647.GD2894@purematrix.com
In Reply to: RE: [gentoo-dev] Portage as a dependency by "Sean P. Kane"
1 I would hope that people rsync before installing new packages -- saves having
2 to install them twice. After the rsync, if you run emerge -up world, you'll
3 get a specific message in the package list about a new portage being
4 available. Isn't this and the general knowledge that Gentoo hinges on portage
5 enough for people to update portage before emerging other packages?
6
7 Alain
8
9
10 On Fri, Feb 07, 2003 at 08:49:38AM -0800, Sean P. Kane wrote:
11 > An example of a package is x11-base/xfree-4.2.1-r2 which requries a
12 > version of Portage that doesn't experience BUG 13013
13 > http://bugs.gentoo.org/show_bug.cgi?id=13013. If people know this it
14 > would be very helpful to either makrk it as a dependency, which may
15 > actually be too difficult for package mantainers to keep updated, or
16 > allow Portage to have an auto-update feature that will always update
17 > Portage before doing other emerges.
18 >
19 > Sean
20 >
21 >
22 > -----Original Message-----
23 > From: Dylan Carlson [mailto:absinthe@×××××.com]
24 > Sent: Thursday, February 06, 2003 19:30
25 > To: Sean P. Kane; gentoo-dev@g.o
26 > Subject: Re: [gentoo-dev] Portage as a dependency
27 >
28 >
29 > On Thursday 06 February 2003 06:17 pm, Sean P. Kane wrote:
30 > > I reported a bug earlier today that turned out to be caused by a
31 > > slightly older version of Portage. Shouldn't we consider having
32 > > portage or the ebuilds handle this type of situation better, by either
33 >
34 > > having the ebuilds have a particular version of portage as a
35 > > dependency or making portage always check for a newer stable version
36 > > of portage whenever it does an emerge and then upgrading to that
37 > > first.
38 >
39 > RDEPEND=">=sys-apps/portage-2.0.47", as an example, is one way an ebuild
40 >
41 > can do it.
42 >
43 > Furthermore, Portage should be backward compatible with ebuilds written
44 > for
45 > earlier versions. DEPEND/RDEPEND should be all that is necessary in
46 > situations where an ebuild depends on a newer, masked version of Portage
47 >
48 > -- if that is in fact necessary.
49 >
50 > Cheers,
51 > Dylan Carlson
52 >
53 > --
54 > gentoo-dev@g.o mailing list
55 >
56 >
57 > --
58 > gentoo-dev@g.o mailing list
59 >
60
61 --
62 gentoo-dev@g.o mailing list

Replies

Subject Author
Re: [gentoo-dev] Portage as a dependency Toby Dickenson <tdickenson@××××××××××××××××××××××××××××.uk>