| 1 |
On Saturday 06 March 2010 02:11:15 Petteri Räty wrote: |
| 2 |
> On 03/05/2010 08:59 PM, Mike Frysinger wrote: |
| 3 |
> > sometimes i have optional patches (ignoring the "patches should always be |
| 4 |
> > applied") where autotools should be run. always inheriting autotools is |
| 5 |
> > currently annoying because it always adds the related dependencies. USE |
| 6 |
> > based inherits are obviously out. |
| 7 |
> > |
| 8 |
> > so unless there's some burgeoning standard i'm not aware of, below is |
| 9 |
> > what i have in mind. packages set AUTOTOOLS_AUTO_DEPEND to "no" before |
| 10 |
> > inheriting autotools.eclass and that allows them to put |
| 11 |
> > ${AUTOTOOLS_DEPEND} behind a USE flag in their own DEPEND string. |
| 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 |
i'm more inclined towards Jonathan's opinion, so ive kept the proposed |
| 18 |
behavior (plus a fix from Torsten). |
| 19 |
-mike |
Archives