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 15:25:54 +0200 [thread overview]
Message-ID: <4DB2D362.4020206@gentoo.org> (raw)
In-Reply-To: <4DB2B4EC.3070901@gentoo.org>
Zac Medico schrieb:
>> Would it make sense to do the following:
>> (1) make all new-style virtuals additionally depend on an old-style
>> virtual (a new category might be appropriate)
>> (2) ebuilds in overlays can PROVIDE the old-style virtual
>>
> It seems like new-style virtual would be introducing complexity without
> adding any value here. Why not just use a pure old-style virtual?
>
The idea is that code for old-style virtuals can be removed from the
package manager (which seems to be one of the goals of getting rid of
old-style virtuals).
>> (3) in a future EAPI, package managers are allowed to ignore the
>> old-style virtual dependency for packages which are not already installed
>>
> I'm not sure what you mean here. In || dependencies, it's normal to
> ignore choices that are masked or unavailable, so I'm not sure that
> you're suggesting anything different from the existing || behavior.
>
Indeed, the old-style virtual will be a non-existing package in the case
of a package manager which doesn't support them.
>> If directly including installed old-style virtual packages in the
>> dependency calculations is not feasible, (3) could be implemented
>> through modifying package.provided like it is already done for
>> package.{keywords,mask,use} after profile/ updates
>>
> Again, I'm not sure that I understand the point of this. Since ||
> dependencies already ignore unavailable or masked choices, why would
> package.provided be needed?
>
Because the package manager might not know about old-style virtuals
during dependency calculation.
Regards,
Chi-Thanh Christopher Nguyen
next prev parent reply other threads:[~2011-04-23 13:27 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 [this message]
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 ` [gentoo-dev] reconciling new-style virtuals with overlays, was: RDEPENDing on packages from overlays? Chí-Thanh Christopher Nguyễn
2011-04-23 11:02 ` [gentoo-dev] " 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=4DB2D362.4020206@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