From: Nikos Chantziaras <realnc@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: virtual/shadow
Date: Tue, 13 Mar 2012 05:46:00 +0200 [thread overview]
Message-ID: <jjmftv$h98$1@dough.gmane.org> (raw)
In-Reply-To: <20120313002317.623e4e26@digimed.co.uk>
On 13/03/12 02:23, Neil Bothwick wrote:
> On Tue, 13 Mar 2012 01:54:30 +0200, Nikos Chantziaras wrote:
>
>>>> Anyone care to offer an opinion on what it will take to get PROVIDES
>>>> support in portage?
>>>
>>> IMO, it would take virtuals causing so many headachy breakages that
>>> some devs started keeping up a steady drumbeat on irc and mailing
>>> lists. When the number of virtual packages gets close to a thousand,
>>> I'd guess that might happen. Then there would be years of discussion
>>> and GLEP proposals, and by EAPI 207 it should be done.
>>
>> The problem isn't the amount of virtuals. This doesn't affect the
>> users much. It's the inability for people to offer replacement
>> packages in overlays.
>
> They could include a modified virtual in the overlay, but your point is
> valid; including the information in the ebuilds is more flexible.
This only works if portage has a virtual. If it doesn't, you're
screwed. You need to also provide modified packages of all ebuilds
depending on the package you're offering a replacement for. As you can
guess, it's not practical.
This leaves only one option; have users put the original package in
package.provided and emerge your replacement as a non-dep (going in
"world".)
next prev parent reply other threads:[~2012-03-13 3:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 18:05 [gentoo-user] virtual/shadow Bruce Hill, Jr.
2012-03-12 18:50 ` Paul Hartman
2012-03-12 19:21 ` Bruce Hill, Jr.
2012-03-12 19:19 ` [gentoo-user] virtual/shadow Nikos Chantziaras
2012-03-12 19:30 ` Bruce Hill, Jr.
2012-03-12 20:29 ` Alan McKinnon
2012-03-12 22:34 ` »Q«
2012-03-12 23:54 ` Nikos Chantziaras
2012-03-13 0:23 ` Neil Bothwick
2012-03-13 3:46 ` Nikos Chantziaras [this message]
2012-03-13 16:04 ` »Q«
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='jjmftv$h98$1@dough.gmane.org' \
--to=realnc@gmail.com \
--cc=gentoo-user@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