| 1 |
On Friday 19 November 2004 10:28, Robin H. Johnson wrote: |
| 2 |
|
| 3 |
> I'd throw all the requirement checking stuff into an eclass, but I do |
| 4 |
> see one thing that would be suitable for portage to have (and it's more |
| 5 |
> broadly useful): |
| 6 |
> Ability to do an arbitary calculation at depend/pretend time so that it |
| 7 |
> can stop the entire emerge process before any packages are |
| 8 |
> unpacked/compiled/installed. |
| 9 |
> |
| 10 |
> Eg portage can calc the deptree, and then before printing it out, it |
| 11 |
> evaluates the testing function for every ebuild in the deptree that has |
| 12 |
> the function. I already see ebuilds that have something similar in |
| 13 |
> pkg_setup(), but that runs too late - it should check things before any |
| 14 |
> installs start. |
| 15 |
> |
| 16 |
> If portage cached which ebuilds had the testing function this makes the |
| 17 |
> evaluation of it O(n) with a very small n. |
| 18 |
> |
| 19 |
> As one place that would definetly use this as well, see PHP packages |
| 20 |
> for combinations of USE flags that are competely incompatible and |
| 21 |
> automatic logic to exclude one of the USE flags is not appropriate |
| 22 |
> (currently we just call die). |
| 23 |
|
| 24 |
As I have proposed something similar yesterday for a different issue, I'd |
| 25 |
like to ask the portage people what they think about it. Of course there |
| 26 |
would be restrictions on this function, but that's acceptable. |
| 27 |
|
| 28 |
Paul |
| 29 |
|
| 30 |
-- |
| 31 |
Paul de Vrieze |
| 32 |
Gentoo Developer |
| 33 |
Mail: pauldv@g.o |
| 34 |
Homepage: http://www.devrieze.net |
Archives