1 |
On 04/30/2011 02:47 PM, Ole Markus With wrote: |
2 |
> Hi all, |
3 |
> |
4 |
> I was thinking of adding SVN snapshot ebuilds of PHP to the tree. |
5 |
> Ebuilds for PHP extensions use USE_EXPAND to decide which slots (and |
6 |
> thus, which ABIs) of PHP the extension should be built for, much like |
7 |
> ruby does. A new USE_EXPAND USE flag should therefore be added for the |
8 |
> SVN snapshot slot. The problem is that the ABI is not stable and should |
9 |
> only be used by people who 'know what they are doing', and the snapshot |
10 |
> ebuilds will probably always be without keywords. This will cause some |
11 |
> dependency problems. |
12 |
> |
13 |
> The only solution I could think of would be to add this new USE flag to |
14 |
> use.mask. But as far as I could tell, use.mask is meant for masking USE |
15 |
> flags that do not work on certain architectures etc. It is also a bit |
16 |
> tricky for users to unmask USE flags. |
17 |
> |
18 |
> Is this still the best way to do this? Or are there any better ways that |
19 |
> I did not think of? |
20 |
> |
21 |
> Cheers, |
22 |
> Ole Markus |
23 |
> |
24 |
|
25 |
I don't see that this is much different in philosophy than p.masking |
26 |
experimental/broken ebuilds which we add to the tree for dev only |
27 |
testing. In both cases a user who thinks they 'know what they're doing' |
28 |
can locally unmask, at their own risk. |
29 |
|
30 |
-- |
31 |
Anthony G. Basile, Ph.D. |
32 |
Gentoo Linux Developer [Hardened] |
33 |
E-Mail : blueness@g.o |
34 |
GnuPG FP : 8040 5A4D 8709 21B1 1A88 33CE 979C AF40 D045 5535 |
35 |
GnuPG ID : D0455535 |