| 1 |
2008-08-02 04:02:48 Zac Medico napisał(a): |
| 2 |
> Hi everyone, |
| 3 |
> |
| 4 |
> It might good to add support for a new RESTRICT=live value in |
| 5 |
> ebuilds. By specifying this value, an ebuild would be able to |
| 6 |
> indicate that it uses src_unpack() to download sources from some |
| 7 |
> type of live repository such as cvs, darcs, git, mercurial, or svn. |
| 8 |
> |
| 9 |
> This new RESTRICT=live value would be useful in at least a couple of |
| 10 |
> ways. One is that it could be used to implement a @live-rebuild |
| 11 |
> package set that's based on RESTRICT instead of INHERITED [1]. It |
| 12 |
> could also be used to implement a more accurate LIVEVCS.stable check |
| 13 |
> in repoman, again based on RESTRICT instead of INHERITED [2]. |
| 14 |
> |
| 15 |
> We already have plans for more advanced live ebuild support, |
| 16 |
> including live update detection, that will involve an EAPI bump [3]. |
| 17 |
> However, the RESTRICT=live value is a simple enhancement that we can |
| 18 |
> add now, without the need for an EAPI bump. Thoughts? |
| 19 |
|
| 20 |
The names of other RESTRICT values are related to features which are |
| 21 |
restricted. The new proposed value is intended for live ebuilds so its |
| 22 |
name should be negation of this feature. I think that something like |
| 23 |
RESTRICT=constant-sources would be better. |
| 24 |
|
| 25 |
-- |
| 26 |
Arfrever Frehtes Taifersar Arahesis |
Archives