| 1 |
On 2008/08/02, Zac Medico <zmedico@g.o> wrote: |
| 2 |
|
| 3 |
> USE flags are something that can be enable or disabled |
| 4 |
|
| 5 |
Here, what the flag would enable/disable is belonging of live packages |
| 6 |
to the @live-rebuild set. Compared to the RESTRICT solution, user |
| 7 |
gains an easy per-package control of this set (sure, the flag would be |
| 8 |
turned on in profiles, so that @live-rebuild is complete by default). |
| 9 |
|
| 10 |
> but the behavior of the src_unpack() method downloading live sources |
| 11 |
> is not something that's generally controlled by a USE flag afaik. |
| 12 |
|
| 13 |
Right, this "live-rebuild" USE flag would not control anything in the |
| 14 |
way the ebuild is executed, but only in the way the package is handled |
| 15 |
by Portage. It's not primary usage of USE flags, sure, but it's not |
| 16 |
completly unusual neither (for instance, take USE flags which are just |
| 17 |
there to trigger some convenience PDEPEND). |
| 18 |
|
| 19 |
|
| 20 |
Anyway, to rephrase / summarize my idea: |
| 21 |
|
| 22 |
- IUSE="live-rebuild" in the ebuild |
| 23 |
==> triggers LIVEVCS.stable repoman check |
| 24 |
|
| 25 |
- IUSE="live-rebuild" in the ebuild, and package is installed, |
| 26 |
and USE flag "live-rebuild" is enabled for this package |
| 27 |
==> makes it belong to the @live-rebuild set |
| 28 |
|
| 29 |
-- |
| 30 |
TGL. |
Archives