From: Stephen Bennett <spb@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] GLEP ??: Metapackages
Date: Sun, 06 Mar 2005 18:12:17 +0000 [thread overview]
Message-ID: <1110132737.9219.10.camel@localhost> (raw)
In-Reply-To: <200503061940.06006.danarmak@gentoo.org>
On Sun, 2005-03-06 at 19:40 +0200, Dan Armak wrote:
> It's a cool idea. What's missing in the proto-GLEP is an explanation of why
> you can't do this with a normal ebuild (that doesn't install any files), and
> need the new concept of metapackages.
The idea is that a metapackage, unlike a normal ebuild, doesn't exist in
the installed package db, and its deps are always inspected when it
turns up in the depgraph. That means that you avoid the situation where
you merge package A, which depends on virtual/x11, and then pulls in
xorg-x11. Then, for whatever reason, you unmerge xorg, and virtual/x11
is still in the vdb, so the next app you merge that deps on it will
break. That was explained in the -dev thread I linked; I probably should
add an explanation into the GLEP.
> There's also the question of portage not checking RDEPENDs when unmerging, so
> you can unmerge a dep (and things will break) but you can't unmerge a package
> providing a virtual (portage will catch that). But the correct solution here,
> if we're going to modify portage, is to add generic RDEPEND checking support
> to emerge unmerge...
Allegedly the new dep resolver that's being worked on should handle
that... not sure if it'll get into the next portage release though. But
agreed, it is needed, and from what I've been given to understand should
handle this situation properly without too much extra effort.
> Also, the GLEP says: "On a side note, this system of metapackages would
> provide an implementation of 'package sets' as proposed in GLEP 21 [2]_."
>
> I don't see how that would happen. A package set exists to install all of a
> list of packages, while a virtual/metapackage exists to install one of a list
> of (often mutually exclusive) packages. These are very different goals. How
> would metapackages help with sets any more than ordinary ebuilds already do?
Since the metapackage has some arbitrary DEPEND string that has to be
met, there's no reason why this couldn't require all packages reckoned
to be part of a set, rather than one of the packages reckoned to provide
a virtual.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-03-06 18:09 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
2005-03-03 0:14 ` James Northrup
2005-03-06 17:40 ` Dan Armak
2005-03-06 18:12 ` Stephen Bennett [this message]
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=1110132737.9219.10.camel@localhost \
--to=spb@gentoo.org \
--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