List Archive: gentoo-dev
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
On Wed, 20 Jun 2012 18:45:31 +0200
Ulrich Mueller <email@example.com> wrote:
> I'd say that EAPI 5 should provide an "apply_patches_here" function
> that can be called by ebuilds, but if the ebuild hasn't called the
> function, then it should fall back to applying user patches just after
But applying user patches after src_prepare is wrong. We already had
> > We had this discussion in the original thread. If we're just looking
> > for a feature that "might work sometimes", there's no point sticking
> > any of this in the EAPI at all.
> I don't see why the above wouldn't work. The user still has complete
> control, because he can always patch (e.g.) configure along with
Not really, since patches mess with timestamps.
> Then there are ebuilds that don't call eautoreconf, in the first
> place. Should we require that all of them inherit autotools now, just
> for the unlikely case that user patches could be applied?
If the aim is to provide a working feature to users, yes. The
alternative is to not provide user patches support.