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