From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Patching of ebuilds
Date: Thu, 29 Jan 2009 10:30:08 -0600 [thread overview]
Message-ID: <58965d8a0901290830n5d248a61r4dfa64c304ab9401@mail.gmail.com> (raw)
In-Reply-To: <49817653.4060802@wht.com.au>
On Thu, Jan 29, 2009 at 3:26 AM, Andrew Lowe <agl@wht.com.au> wrote:
> Hi all,
> I've had a look on the web but can't seem to find any instructions on
> how to do the patching of ebuilds. I have the situation where I've tried to
> install the media centre app MMSV2. I've done the emerge, a lot of dependent
> functionality was compiled and now it's up to compiling the actual MMSV2.
> When compiling, an error happens. I had a look in bugs.gentoo.org and there
> is a bug in there that covers, I think, the failure.
>
> Attached to the bug is a patch that someone has developed. I now want
> to use this patch to patch the ebuild and see if it really does fix the
> problem. My problem is that I don't know the actual steps needed to do the
> patching. I know about the patch utility but I don't know where the actual
> files are, and how I should do the patching so that Portage does not view
> the patched files as corrupt and therefore won't do the emerge.
>
> If someone can tell me how, or point me to a webpage that tells me
> how, to do the patching it would be greatly appreciated.
>
> Regards,
> Andrew
You can usually use the "ebuild" command to do the portage steps
separately, so after unpacking you can change to the portage tmpdir
and apply the patch from bugzilla. Then proceed with the making and
installing steps with "ebuild".
prev parent reply other threads:[~2009-01-29 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 9:26 [gentoo-user] Patching of ebuilds Andrew Lowe
2009-01-29 9:28 ` Justin
2009-01-29 9:55 ` Jesús Guerrero
2009-01-29 16:09 ` [gentoo-user] " James
2009-01-29 16:30 ` 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=58965d8a0901290830n5d248a61r4dfa64c304ab9401@mail.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