| 1 |
On Mon, 9 Jun 2014 18:31:27 +0200 |
| 2 |
Michał Górny <mgorny@g.o> wrote: |
| 3 |
|
| 4 |
> Sounds insanely complex for a minor issue. What's the problem with |
| 5 |
> ebuilds calling 'default' in src_prepare() to get user patches applied |
| 6 |
> (and possibly ${PATCHES[@]} as well)? |
| 7 |
|
| 8 |
Because the nicer solution is to not call some_function() in every |
| 9 |
single ebuild in the tree that happens to stray from the default |
| 10 |
src_prepare(). |
| 11 |
|
| 12 |
The problem is in what needs to happen after epatch_user(). If it turns |
| 13 |
out some files need to be re-generated, then that would call for a |
| 14 |
post-src_prepare() function (src_regen() perhaps) that all the |
| 15 |
eautoreconf and equivalent calls get moved away to. Which then leads to |
| 16 |
problems in determining whether that's needed, and to the user having |
| 17 |
no proper way to force it as of now. |
| 18 |
|
| 19 |
|
| 20 |
jer |
Archives