public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sean P. Kane" <spkane@genomatica.com>
To: <gentoo-dev@gentoo.org>
Subject: RE: [gentoo-dev] Portage as a dependency
Date: Tue, 11 Feb 2003 08:54:14 -0800	[thread overview]
Message-ID: <C42D120999B1CC4C886B6BB2832F356019BB6E@hermes.genomatica.com> (raw)

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] 
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 
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 
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 
> http://bugs.gentoo.org/show_bug.cgi?id=13013. 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]
> 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 
> > slightly older version of Portage. Shouldn't we consider having 
> > portage or the ebuilds handle this type of situation better, by 
> > either
> 
> > having the ebuilds have a particular version of portage as a 
> > dependency or making portage always check for a newer stable version

> > of portage whenever it does an emerge and then upgrading to that 
> > first.
> 
> RDEPEND=">=sys-apps/portage-2.0.47", as an example, is one way an
> ebuild
> 
> can do it.    
> 
> Furthermore, Portage should be backward compatible with ebuilds
> written for earlier versions.  DEPEND/RDEPEND should be all that is 
> necessary in 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
> 

--
gentoo-dev@gentoo.org mailing list


--
gentoo-dev@gentoo.org mailing list


             reply	other threads:[~2003-02-11 17:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-11 16:54 Sean P. Kane [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-07 18:32 [gentoo-dev] Portage as a dependency Eugene Wong
2003-02-07 17:06 Sean P. Kane
2003-02-07 16:49 Sean P. Kane
2003-02-07 17:06 ` Alain Penders
2003-02-07 17:34   ` Toby Dickenson
2003-02-06 23:17 Sean P. Kane
2003-02-07  3:30 ` Dylan Carlson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C42D120999B1CC4C886B6BB2832F356019BB6E@hermes.genomatica.com \
    --to=spkane@genomatica.com \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox