1 |
For those of you who don't know, check-reqs is an eclass that is |
2 |
occasionally used by a few packages that have ludicrously high build |
3 |
requirements. Typical examples have included anything using Haskell (the |
4 |
programming language with built-in memory leaks!) and certain C++ |
5 |
template metaprogamming voodoo. |
6 |
|
7 |
Currently it just exports a single function that will warn (or die, |
8 |
based upon user preference) if the build requirements aren't met. There |
9 |
has been a request for a clean way of handling packages that can be |
10 |
built in two different ways that give the same end result (typical |
11 |
example is use of a really slow but low memory requiring algorithm vs a |
12 |
fast but memory intensive algorithm when building data tables). |
13 |
|
14 |
How does something like the attached look? (Yes, it's using old-school |
15 |
[ rather than [[, since the rest of the eclass is written that way. I |
16 |
might switch the whole thing over at some point.) |
17 |
|
18 |
-- |
19 |
Ciaran McCreesh : Gentoo Developer (Wearer of the shiny hat) |
20 |
Mail : ciaranm at gentoo.org |
21 |
Web : http://dev.gentoo.org/~ciaranm |