| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Thomas de Grenier de Latour wrote: |
| 5 |
> On 2008/08/01, Zac Medico <zmedico@g.o> wrote: |
| 6 |
> |
| 7 |
>> It might good to add support for a new RESTRICT=live value in |
| 8 |
>> ebuilds. |
| 9 |
> |
| 10 |
> Since some people have a problem with this flag being put there, what |
| 11 |
> about IUSE=live-rebuild as an alternative? It's "use.desc" would be |
| 12 |
> something like "add this package to the @live-rebuild set (only for |
| 13 |
> Portage 2.2_rc6 and above)". And the set implementation would be |
| 14 |
> modified to only include packages for which this flag is enabled. |
| 15 |
> |
| 16 |
|
| 17 |
That's an interesting idea, however I think RESTRICT is a better fit |
| 18 |
for the attribute that we're trying to model. USE flags are |
| 19 |
something that can be enable or disabled but the user but the |
| 20 |
behavior of the src_unpack() method downloading live sources is not |
| 21 |
something that's generally controlled by a USE flag afaik. Are there |
| 22 |
any existing ebuilds that allow src_unpack to be toggled in this way |
| 23 |
via a USE flag? Is this something that would be desireable? |
| 24 |
|
| 25 |
Zac |
| 26 |
-----BEGIN PGP SIGNATURE----- |
| 27 |
Version: GnuPG v2.0.9 (GNU/Linux) |
| 28 |
|
| 29 |
iEYEARECAAYFAkiVAtsACgkQ/ejvha5XGaNWLwCgvOkEutL+2IYGF5Nz0ncH1GL/ |
| 30 |
k/8An3lwrLOUKKFaTNMVaYBLd0OryI67 |
| 31 |
=6uSV |
| 32 |
-----END PGP SIGNATURE----- |
Archives