public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Chí-Thanh Christopher Nguyễn" <chithanh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] reconciling new-style virtuals with overlays, was: RDEPENDing on packages from overlays?
Date: Sat, 23 Apr 2011 18:02:07 +0200	[thread overview]
Message-ID: <4DB2F7FF.8040201@gentoo.org> (raw)
In-Reply-To: <20110423155724.040acfc0@googlemail.com>

Ciaran McCreesh schrieb:
> On Sat, 23 Apr 2011 16:47:37 +0200
> Chí-Thanh Christopher Nguyễn <chithanh@gentoo.org> wrote:
>   
>> What I propose solves the problems that old-style virtuals introduce
>> in dependency resolution.
>>     
> Not really, because it means we'd have to keep the nasty old code around
> forever. If we just do away with the things entirely instead then we
> can pretend they never existed (like we did for ? : dependencies).
>   

We can mostly pretend that they never existed. PROVIDE will only be
relevant during the installation phase.

>> What other problems do they cause?
>>     
> DEPEND=">=virtual/blah-2"
>
> DEPEND="virtual/blah[foo]"
>
> DEPEND="!virtual/that-i-provide"
>
> PROVIDE="not-a/virtual"
>   
Would be ignored during dependency calculation and become
not-a/virtual-<version> in package.provided later.
> best_version virtual/blah
>
> The full VDB load required to figure out whether or not a virtual is
> installed

Problems I had indeed not taken into account are !virtual/foo
dependencies and USE flags in package.provided (not allowed yet, bug
142941). But the former are also not going to work any more if new-style
virtuals are used instead of old-style, as you block only the virtuals
and not their providers.

If the USE flag problem is considered a show-stopper, then I have to
take back my proposal until bug 142941 is fixed.


Regards,
Chi-Thanh Christopher Nguyen




  parent reply	other threads:[~2011-04-23 16:03 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-23  6:05 [gentoo-dev] RDEPENDing on packages from overlays? Eray Aslan
2011-04-23 10:28 ` [gentoo-dev] reconciling new-style virtuals with overlays, was: " Chí-Thanh Christopher Nguyễn
2011-04-23 11:15   ` Zac Medico
2011-04-23 13:25     ` Chí-Thanh Christopher Nguyễn
2011-04-23 11:32   ` Ciaran McCreesh
2011-04-23 13:28     ` Chí-Thanh Christopher Nguyễn
2011-04-23 13:37       ` Ciaran McCreesh
2011-04-23 14:47         ` Chí-Thanh Christopher Nguyễn
2011-04-23 14:57           ` Ciaran McCreesh
2011-04-23 15:50             ` [gentoo-dev] reconciling new-style virtuals with overlays Ulrich Mueller
2011-04-23 16:02             ` Chí-Thanh Christopher Nguyễn [this message]
2011-04-23 11:02 ` [gentoo-dev] RDEPENDing on packages from overlays? Zac Medico
2011-04-23 12:01   ` Nathan Phillip Brink
2011-04-23 12:07   ` Thomas Sachau
2011-04-23 12:08     ` Ciaran McCreesh
2011-04-23 13:05     ` Ulrich Mueller
2011-04-23 15:24       ` Zac Medico
2011-04-24  4:57         ` Eray Aslan
2011-04-24  5:39           ` Ulrich Mueller
2011-04-24  6:42             ` Eray Aslan
2011-04-24 20:35               ` William Hubbs
2011-04-23 11:03 ` William Hubbs
2011-04-23 13:07   ` Chí-Thanh Christopher Nguyễn
2011-04-23 11:08 ` [gentoo-dev] " Diego Elio Pettenò
2011-04-23 11:34 ` [gentoo-dev] " Ciaran McCreesh
2011-04-23 11:59 ` Thomas Sachau

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=4DB2F7FF.8040201@gentoo.org \
    --to=chithanh@gentoo.org \
    --cc=gentoo-dev@lists.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