| 1 |
Am Samstag, den 28.04.2012, 18:14 +0100 schrieb Ciaran McCreesh: |
| 2 |
> On Sat, 28 Apr 2012 19:11:03 +0200 |
| 3 |
> Tiziano Müller <dev-zero@g.o> wrote: |
| 4 |
> > Could we also get an interface to disk- and memory-space requirements? |
| 5 |
> > |
| 6 |
> > Something like: |
| 7 |
> > |
| 8 |
> > EREQUIRE_DISK="2G" |
| 9 |
> > EREQUIRE_MEMORY="1G" |
| 10 |
> > |
| 11 |
> > which gets checked in pre_pkg_setup? |
| 12 |
> |
| 13 |
> Is there anything the package mangler can do better than check-reqs |
| 14 |
> here? |
| 15 |
> |
| 16 |
|
| 17 |
Since $T isn't writeable in pkg_pretend according to EAPI it doesn't |
| 18 |
make much sense to read from it as well (since it is empty). Therefore a |
| 19 |
PM may decide to dynamically allocate $S and/or $T after pkg_pretend. Or |
| 20 |
is there something I forgot? |
| 21 |
|
| 22 |
Furthermore, just because disk space requirements are met at pkg_pretend |
| 23 |
time it may not be the case at src_unpack or src_compile time and one |
| 24 |
may have to recheck it (especially when using cave-resolve with -Ci). |
| 25 |
|
| 26 |
And since the PM is responsible for preparing the environment it also |
| 27 |
makes sense to me that the PM checks whether it can prepare the |
| 28 |
environment at all as required by the ebuild. |
| 29 |
|
| 30 |
Cheers, |
| 31 |
Tiziano |
Archives