From: Ian Stakenvicius <axs@gentoo.org>
To: "gentoo-dev@lists.gentoo.org" <gentoo-dev@lists.gentoo.org>
Cc: "gentoo-dev@lists.gentoo.org" <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Re: Making user patches globally available
Date: Sun, 15 Apr 2012 09:46:41 -0400 [thread overview]
Message-ID: <EE0C2560-CB73-45B9-A377-1F8D27949B09@gentoo.org> (raw)
In-Reply-To: <20120415030326.0355ecf2@gentoo.org>
On 2012-04-15, at 5:03 AM, Ryan Hill <dirtyepic@gentoo.org> wrote:
> On Sun, 15 Apr 2012 01:35:40 -0700
> Zac Medico <zmedico@gentoo.org> wrote:
>
>> On 04/15/2012 01:16 AM, Ryan Hill wrote:
>>> Right now we have support in some packages for user patches - those being
>>> patches dropped into /etc/portage/patches/pkgname/ - which are automatically
>>> applied. Because this feature is implemented by epatch_user() in
>>> eutils.eclass, it is only available for ebuilds that inherit eutils and
>>> explicitly call epatch_user or inherit another eclass that calls it in an
>>> exported phase (eg. base). The end result is a very inconsistent experience,
>>> where user patches may or may not work not only on a package-by-package
>>> basis, but ebuild-by-ebuild.
>>>
>>> Is there any reason why this couldn't just be done in the package manager,
>>> making user patches available for all ebuilds without code changes?
>>
>> Funtoo has support for FEATURES=localpatch, which does the epatch_user
>> thing before src_prepare. I think it should really go after src_prepare,
>> in order to apply patches after those that src_prepare may apply
>> (avoiding possible conflicts).
>
> I agree.
>
>> The reason that Funtoo's FEATURES=localpatch applies patches before
>> src_prepare is that it's common for eautoreconf to be called inside
>> src_prepare, and applying patches after src_prepare can create a need to
>> call eautoreconf a second time.
>
> Well that could waste a bit of time but is pretty much harmless, no? And the
> existing usages of epatch_user (other than autotools-utils) don't eautoreconf
> anyways, nor should they in case the package doesn't use autotools.
>
>
the existing use of epatch_user allow you to put the call after current epatchez and before the eautoreconf call..
I agree tho -- an automatic call to eautoreconf could be triggered by features=localpatch whenever there are patches and autotools.eclass is inherited.
also, any user patches applied could be cat'd to the build log, to allow for debugging ....
next prev parent reply other threads:[~2012-04-15 13:47 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-15 8:16 [gentoo-dev] Making user patches globally available Ryan Hill
2012-04-15 8:35 ` Zac Medico
2012-04-15 9:03 ` [gentoo-dev] " Ryan Hill
2012-04-15 9:12 ` Zac Medico
2012-04-15 13:46 ` Ian Stakenvicius [this message]
2012-04-23 5:04 ` Steven J Long
2012-04-23 5:56 ` Zac Medico
2012-04-28 0:28 ` [gentoo-dev] " Steven J Long
2012-04-18 16:59 ` [gentoo-dev] " Jeroen Roovers
2012-04-18 17:39 ` Mike Frysinger
2012-04-18 17:41 ` Ciaran McCreesh
2012-04-18 18:20 ` Zac Medico
2012-04-18 18:34 ` David Leverton
2012-04-18 19:41 ` Zac Medico
2012-04-18 19:47 ` Michał Górny
2012-04-18 21:41 ` David Leverton
2012-04-26 4:44 ` [gentoo-dev] " Ryan Hill
2012-04-26 5:03 ` Zac Medico
2012-04-26 6:09 ` Ryan Hill
2012-04-26 6:18 ` Duncan
2012-04-26 6:26 ` Zac Medico
2012-04-26 9:55 ` Duncan
2012-04-26 15:21 ` Zac Medico
2012-04-26 22:08 ` Duncan
2012-04-27 1:41 ` Zac Medico
2012-04-27 14:15 ` Duncan
2012-04-27 14:20 ` Michał Górny
2012-04-27 17:19 ` Zac Medico
2012-04-27 18:01 ` Ulrich Mueller
2012-04-27 18:10 ` Zac Medico
2012-04-27 18:42 ` Alec Warner
2012-04-27 18:57 ` Michał Górny
2012-04-27 19:26 ` Zac Medico
2012-04-27 19:26 ` Ciaran McCreesh
2012-04-27 19:43 ` Ulrich Mueller
2012-04-27 19:58 ` Michał Górny
2012-04-27 20:12 ` EAPI 5 (Was: Re: [gentoo-dev] Re: Making user patches globally available) Ciaran McCreesh
2012-04-28 8:40 ` Pacho Ramos
2012-04-28 8:52 ` Michał Górny
2012-04-28 9:34 ` Ciaran McCreesh
2012-04-28 10:09 ` Francesco Riosa
2012-04-28 15:16 ` Ciaran McCreesh
2012-04-27 14:27 ` [gentoo-dev] Re: Making user patches globally available Ciaran McCreesh
2012-04-27 15:41 ` Zac Medico
2012-04-27 15:45 ` Ciaran McCreesh
2012-04-27 15:55 ` Zac Medico
2012-04-27 16:00 ` Ciaran McCreesh
2012-04-27 16:08 ` Zac Medico
2012-04-27 16:11 ` Ciaran McCreesh
2012-04-27 16:19 ` Zac Medico
2012-04-27 15:55 ` Nikos Chantziaras
2012-04-28 2:29 ` Duncan
2012-04-26 18:27 ` Michał Górny
2012-04-26 18:43 ` Zac Medico
2012-04-26 18:50 ` Michał Górny
2012-04-26 18:55 ` Ciaran McCreesh
2012-04-15 8:53 ` [gentoo-dev] " Patrick Lauer
2012-04-15 9:18 ` [gentoo-dev] " Ryan Hill
2012-04-15 9:25 ` [gentoo-dev] " Sergei Trofimovich
2012-04-15 23:34 ` [gentoo-dev] " Duncan
2012-04-15 11:00 ` [gentoo-dev] " Andreas K. Huettel
2012-04-15 13:55 ` Michał Górny
2012-04-15 22:19 ` William Hubbs
2012-04-16 8:12 ` Michał Górny
2012-04-15 14:01 ` Michał Górny
2012-04-15 16:25 ` Mike Frysinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=EE0C2560-CB73-45B9-A377-1F8D27949B09@gentoo.org \
--to=axs@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox