| 1 |
Le jeudi 01 avril 2010 à 00:56 -0700, Brian Harring a écrit : |
| 2 |
[snip] |
| 3 |
> pkg_setup: ran just before the build of the pkg, after the pkg's |
| 4 |
> DEPENDS are all built. Meaning you *can* do has_version checks, |
| 5 |
> kernel config checks, etc, because the proceeding deps are now |
| 6 |
> satisfied. |
| 7 |
> |
| 8 |
> pkg_pretend: ran before *every* *single* *build* has been ran, |
| 9 |
> meaning |
| 10 |
> the has_version check, the kernel config check, etc, all can |
| 11 |
> invalidly |
| 12 |
> die. |
| 13 |
> |
| 14 |
> Had they been pkg_setup (check after DEPENDs are satisfied), the |
| 15 |
> majority of the checks would pass, but because they're ran prior to |
| 16 |
> DEPENDs satisfied, users will have to wind up breaking what was a |
| 17 |
> single emerge invocation into multiple to satisfy pkg_pretend being |
| 18 |
> wrong. |
| 19 |
> |
| 20 |
|
| 21 |
jumping on the train here, but who said PM would not feed proper data to |
| 22 |
pkg_pretend so it would behave like the DEPEND were already built. Could |
| 23 |
some guy involved in a PM development tell us about how this would be |
| 24 |
handled ? |
| 25 |
|
| 26 |
-- |
| 27 |
Gilles Dartiguelongue <eva@g.o> |
| 28 |
Gentoo |
Archives