From: Chris Gianelloni <wolf31o2@gentoo.org>
To: Chris Wolfe <cwolfe@globetrotter.qc.ca>
Cc: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Local patches and emerge
Date: Wed, 12 May 2004 13:19:49 -0400 [thread overview]
Message-ID: <1084382388.7729.68.camel@localhost> (raw)
In-Reply-To: <40A253DE.5010403@globetrotter.qc.ca>
[-- Attachment #1: Type: text/plain, Size: 922 bytes --]
On Wed, 2004-05-12 at 12:42, Chris Wolfe wrote:
> Any way to get emerge to add local patches without having to modify the
> ebuild in question?
>
> Am currently putting together a server on which a fair number of the
> packages have needed tweaking at the source level to get required
> functionality. At the moment I am using ebuild unpack, then patching and
> running compile install and qmerge. If there is no easy solution at the
> moment I will probably just tweak emerge to add a directory to look in for
> local patches.
Wouldn't it just be *much* quicker to add a simple
epatch ${FILESDIR}/patchname
line to the ebuild and keep a local copy in your overlay? I would think
trying to modify emerge itself seems a bit of a wasted effort
considering how easy it is to keep your own overlay.
--
Chris Gianelloni
Developer, Gentoo Linux
Games Team
Is your power animal a penguin?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-05-12 17:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 16:42 [gentoo-dev] Local patches and emerge Chris Wolfe
2004-05-12 17:19 ` Chris Gianelloni [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=1084382388.7729.68.camel@localhost \
--to=wolf31o2@gentoo.org \
--cc=cwolfe@globetrotter.qc.ca \
--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