public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Warner <warnera6@egr.msu.edu>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] GLEP ??: Metapackages
Date: Wed, 02 Mar 2005 15:58:32 -0500	[thread overview]
Message-ID: <422628F8.8040807@egr.msu.edu> (raw)
In-Reply-To: <1109715352.3788.42.camel@localhost>

Stephen Bennett wrote:

>As those who hang around in the mysterious realms of Portage development
>may know, there's some feeling around that the current system of virtual
>packages has some serious limitations. The currently-proposed
>alternative (as discussed previously, notably in
>http://thread.gmane.org/gmane.linux.gentoo.devel/18922), involves a
>system of metapackages. These would essentially consist of a 
>non-installable ebuild that consists entirely of a set of dependency
>information. Once the dependencies for the metapackage are satisfied,
>it's considered to be installed, and packages depending on it can go
>ahead and be built.
>
>This approach brings several advantages over the current system,
>particularly: 
>- Allowing one version of a package to provide a different version of a
>virtual, where these are necessary.
>- Fixing the screwup with .51's virtual handling whereby gcc-2.95.x has
>PROVIDE="sys-apps/texinfo", a package depends on >=texinfo-4.6, so
>portage tries to install >=gcc-4.6.
>- Provides, in one easily accessible place, a list of package that could
>be used to satisfy the dependency. This has advantages for speed (no
>searching the tree for PROVIDEs) and for user-friendliness.
>
>Anyway, with portage development as it is now, this got brought up
>again, and the current state of the GLEP can be found at
>http://dev.gentoo.org/~spb/metapkg-glep.txt. Comments/suggestions/flames
>welcome.
>
>  
>
As long as you keep the PROVIDES line in the ebuild.  Assuming repoman 
does full tree check  when commiting it can make sure that all packages 
that PROVIDE virtual also exist in the metapackage.  That would be my 
only concern, people forgetting to add lines to the correct files :)

>--
>gentoo-dev@gentoo.org mailing list
>  
>
--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2005-03-02 20:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-01 22:15 [gentoo-dev] GLEP ??: Metapackages Stephen Bennett
2005-03-02 12:30 ` Paul de Vrieze
2005-03-02 20:58 ` Alec Warner [this message]
2005-03-03  0:14   ` James Northrup
2005-03-06 17:40 ` Dan Armak
2005-03-06 18:12   ` Stephen Bennett
2005-03-06 19:20     ` Dan Armak
2005-03-07 10:26 ` Thomas de Grenier de Latour
2005-03-07 17:45   ` Stephen Bennett
2005-03-15 12:21 ` Thomas de Grenier de Latour

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=422628F8.8040807@egr.msu.edu \
    --to=warnera6@egr.msu.edu \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-dev@robin.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