| 1 |
On 03/05/2010 08:59 PM, Mike Frysinger wrote: |
| 2 |
> sometimes i have optional patches (ignoring the "patches should always be |
| 3 |
> applied") where autotools should be run. always inheriting autotools is |
| 4 |
> currently annoying because it always adds the related dependencies. USE based |
| 5 |
> inherits are obviously out. |
| 6 |
> |
| 7 |
> so unless there's some burgeoning standard i'm not aware of, below is what i |
| 8 |
> have in mind. packages set AUTOTOOLS_AUTO_DEPEND to "no" before inheriting |
| 9 |
> autotools.eclass and that allows them to put ${AUTOTOOLS_DEPEND} behind a USE |
| 10 |
> flag in their own DEPEND string. |
| 11 |
> |
| 12 |
|
| 13 |
What we use in Java is JAVA_PKG_OPT_USE to declare what use flag the |
| 14 |
DEPENDs should be under. This approach doesn't allow the ebuild |
| 15 |
maintainer to forget adding the depends. |
| 16 |
|
| 17 |
Regards, |
| 18 |
Petteri |
Archives