From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Automatic picking up the patches from /etc/portage/patches
Date: Wed, 04 Jan 2012 08:03:51 -0600 [thread overview]
Message-ID: <4F045C47.3000009@gmail.com> (raw)
In-Reply-To: <20120104154704.f26a777f.v_2e@ukr.net>
On 01/04/2012 07:47 AM, v_2e@ukr.net wrote:
> Hello!
> I have noticed that with portage version changes its behaviour
> regarding the automatic patch catching (from /etc/portage/patches, for
> example) also changes. Some previous versions of portage did apply the
> patches from that directory while the most recent one does not.
>
> I consider this auto-patching feature quite useful and would like to
> use it, but currently I don't know how to do that.
> And also, is portage supposed to pick the patches up automatically or
> not in general?
They are only picked up if the ebuild specifically calls epatch_user
function.
However, you can define this in your /etc/portage/bashrc to have
appended to all ebuilds (who don't already define this function):
post_src_prepare() {
epatch_user
}
then it will call it after it does its normal patching...
For example, I dropped a patch from BGO for xloadimage to make it build
against new libtiff into
/etc/portage/patches/media-gfx/xloadimage-4.1-r11 and emerge, I see this
in emerge output:
>>> Preparing source in
/var/tmp/portage/media-gfx/xloadimage-4.1-r11/work/xloadimage.4.1 ...
* Applying xloadimage-4.1-gentoo-r1.diff ... [ ok ]
* Applying xloadimage-4.1-zio-shell-meta-char.diff ... [ ok ]
* Applying xloadimage-4.1-endif.patch ... [ ok ]
* Applying xloadimage-4.1-include-errno_h.patch ... [ ok ]
* Applying xloadimage-gentoo.patch ... [ ok ]
* Applying xloadimage-4.1-unaligned-access.patch ... [ ok ]
* Applying xloadimage-4.1-ldflags_and_exit.patch ... [ ok ]
* Applying xloadimage-4.1-libpng15.patch ... [ ok ]
* Applying xloadimage-4.1-bracket.patch ... [ ok ]
* Running eautoreconf in
'/var/tmp/portage/media-gfx/xloadimage-4.1-r11/work/xloadimage.4.1' ...
* Running aclocal ... [ ok ]
* Running autoconf ... [ ok ]
* Running autoheader ... [ ok ]
>>> Source prepared.
* Applying user patches from
/etc/portage/patches//media-gfx/xloadimage-4.1-r11 ...
* xloadimage-4.1-tiff.patch ... [ ok ]
* Done with patching
>>> Configuring source in
/var/tmp/portage/media-gfx/xloadimage-4.1-r11/work/xloadimage.4.1 ...
prev parent reply other threads:[~2012-01-04 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 13:47 [gentoo-user] Automatic picking up the patches from /etc/portage/patches v_2e
2012-01-04 14:02 ` Hinnerk van Bruinehsen
2012-01-04 14:03 ` Paul Hartman [this message]
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=4F045C47.3000009@gmail.com \
--to=paul.hartman+gentoo@gmail.com \
--cc=gentoo-user@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