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