| 1 |
On Mon, 7 May 2012 18:41:30 +0200 |
| 2 |
Michał Górny <mgorny@g.o> wrote: |
| 3 |
> On Mon, 07 May 2012 12:19:40 -0400 |
| 4 |
> Michael Orlitzky <michael@××××××××.com> wrote: |
| 5 |
> > On 05/07/12 11:17, Ulrich Mueller wrote: |
| 6 |
> > > |
| 7 |
> > > After all, this functionality is just a stop-gap measure for users |
| 8 |
> > > to apply quick bug fixes, so I don't expect that it will be used |
| 9 |
> > > very often. Even fewer cases will require that eautoreconf is |
| 10 |
> > > called. Do we really want to force developers to put this function |
| 11 |
> > > call into every ebuild? That would be out of proportion, IMHO. |
| 12 |
> > |
| 13 |
> > Only the ebuilds that override src_prepare (which is a lot). |
| 14 |
> |
| 15 |
> The reason for src_prepare() was to simplify ebuilds (so they don't |
| 16 |
> have to override whole src_unpack()). Requiring a specific line in |
| 17 |
> every src_prepare() call means going the other way. |
| 18 |
|
| 19 |
The goal is not simplicity. The goal is the simplest solution that |
| 20 |
works. Catching problems early on is a huge advantage. |
| 21 |
|
| 22 |
-- |
| 23 |
Ciaran McCreesh |
Archives