1 |
On 08/16/2011 12:40 AM, Michał Górny wrote: |
2 |
> On Tue, 16 Aug 2011 00:26:41 -0700 |
3 |
> Zac Medico <zmedico@g.o> wrote: |
4 |
>> On 08/16/2011 12:01 AM, Micha? Górny wrote: |
5 |
>>>>> Considering the number of different virtuals in this category, |
6 |
>>>>> maybe it would be a good idea to split it a little? What I'm |
7 |
>>>>> proposing is maybe creating some kind of '*-virtual' categories. |
8 |
>>>>> |
9 |
>>>>> For example, half of the current virtuals are prefixed with |
10 |
>>>>> 'perl-'. Maybe they could be transformed into 'perl-virtual/*'? |
11 |
>>>> |
12 |
>>>> If you're going to do that, then I'd suggest giving them some sort |
13 |
>>>> of tag that the package manager can rely upon in order to identify |
14 |
>>>> them as virtuals. For example, we could have the ebuilds set |
15 |
>>>> PROPERTIES=virtual [2], or we could simply specify (in PMS) that |
16 |
>>>> any category whose name matches the '*-virtual' pattern will |
17 |
>>>> contain virtuals. |
18 |
>>> |
19 |
>>> Doesn't DEFINED_PHASES==- serve that purpose nowadays? |
20 |
> |
21 |
>> Actually, since EAPI 4 we have default src_install, so it's possible |
22 |
>> to have ebuilds that have no defined phases but still install stuff. |
23 |
> |
24 |
> + empty SRC_URI? I guess something like the workdir fallback conditions |
25 |
> in PMS. |
26 |
|
27 |
When you consider that "live" ebuilds can have empty SRC_URI and |
28 |
download things during src_unpack, it seems more sensible and simple to |
29 |
introduce PROPERTIES="live" or something like it. That way, we'll have a |
30 |
simple boolean flag and won't have to make any fragile assumptions. |
31 |
-- |
32 |
Thanks, |
33 |
Zac |