| 1 |
On 03/07/2010 07:42 PM, Mike Frysinger wrote: |
| 2 |
> On Saturday 06 March 2010 02:11:15 Petteri Räty wrote: |
| 3 |
>> On 03/05/2010 08:59 PM, Mike Frysinger wrote: |
| 4 |
>>> sometimes i have optional patches (ignoring the "patches should always be |
| 5 |
>>> applied") where autotools should be run. always inheriting autotools is |
| 6 |
>>> currently annoying because it always adds the related dependencies. USE |
| 7 |
>>> based inherits are obviously out. |
| 8 |
>>> |
| 9 |
>>> so unless there's some burgeoning standard i'm not aware of, below is |
| 10 |
>>> what i have in mind. packages set AUTOTOOLS_AUTO_DEPEND to "no" before |
| 11 |
>>> inheriting autotools.eclass and that allows them to put |
| 12 |
>>> ${AUTOTOOLS_DEPEND} behind a USE flag in their own DEPEND string. |
| 13 |
>> |
| 14 |
>> What we use in Java is JAVA_PKG_OPT_USE to declare what use flag the |
| 15 |
>> DEPENDs should be under. This approach doesn't allow the ebuild |
| 16 |
>> maintainer to forget adding the depends. |
| 17 |
> |
| 18 |
> i'm more inclined towards Jonathan's opinion, so ive kept the proposed |
| 19 |
> behavior (plus a fix from Torsten). |
| 20 |
> -mike |
| 21 |
|
| 22 |
And what about my latest response to him? |
| 23 |
|
| 24 |
Regards, |
| 25 |
Petteri |
Archives