public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: emerging procmail failure
Date: Thu, 11 Jun 2009 09:25:21 -0500	[thread overview]
Message-ID: <58965d8a0906110725g120bd103vf4a49dafab704e0c@mail.gmail.com> (raw)
In-Reply-To: <uski7tl7i.fsf@newsguy.com>

On Thu, Jun 11, 2009 at 12:04 AM, Harry Putnam<reader@newsguy.com> wrote:
> Paul Hartman <paul.hartman+gentoo@gmail.com> writes:
>
>> On Wed, Jun 10, 2009 at 3:03 PM, Harry Putnam<reader@newsguy.com> wrote:
>>>
>>> Yes... except _OH CRAP_ I've forgotten whatever little tiny skill I once
>>> had to add a patch into the emerge process manually.
>>
>> man ebuild
>>
>> HTH :)
>
> Doesn't any manual patching have to be done in an overlay?  My own
> portage setup.  Then stepped thru with ebuild to get it accepted by
> emerge?
>
> I see no hits at all on either `overlay' or `layman' in man ebuild.
> There must be more to the story than just running ebuild commands. And
> expect the modified ebuild to be accepted by emerge.

Sorry, I was thinking you would apply the patch manually as a
one-off... which you could do by unpacking using the ebuild command,
applying patch, then compiling/merging it. If you want to make your
own ebuild then yes you'd most likely want to put it in an overlay.



  parent reply	other threads:[~2009-06-11 14:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-10 17:14 [gentoo-user] emerging procmail failure Harry Putnam
2009-06-10 19:45 ` Johám-Luís Miguéns Vila
2009-06-10 20:03   ` [gentoo-user] " Harry Putnam
2009-06-10 20:15     ` Paul Hartman
2009-06-11  5:04       ` Harry Putnam
2009-06-11  7:40         ` Neil Bothwick
2009-06-11 14:25         ` Paul Hartman [this message]
2009-06-11  5:19       ` Harry Putnam
2009-06-10 20:54     ` Johám-Luís Miguéns Vila
2009-06-10 21:02     ` Johám-Luís Miguéns Vila

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=58965d8a0906110725g120bd103vf4a49dafab704e0c@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