| 1 |
On Sat, 2005-08-27 at 14:00 +0200, Diego 'Flameeyes' Pettenò wrote: |
| 2 |
> I was wondering last night with az about the handling of autotools. |
| 3 |
> They not always require to be re-run by scratch, but when you have to run |
| 4 |
> aclocal you usually have to run everything after that. |
| 5 |
> Every ebuild handles them in a different way, some ebuilds run them in a && |
| 6 |
> list and then || die, others runs them one-by-one. |
| 7 |
> Some force updating of support files and some don't. |
| 8 |
> Some adds code to let them print the status to the screen, some hides the |
| 9 |
> actual output and some don't. |
| 10 |
> |
| 11 |
|
| 12 |
I still think a autoreconf is usually enough, except for cases where |
| 13 |
that do not work, and then something like this will not work anyhow. |
| 14 |
|
| 15 |
Anyhow, if you insist, then rather something like attached. |
| 16 |
|
| 17 |
PS: elibtoolize is a problem as it might collide with the one from |
| 18 |
libtool.eclass |
| 19 |
|
| 20 |
|
| 21 |
-- |
| 22 |
Martin Schlemmer |
Archives