public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Lieb <chris.lieb@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Using portage through NFS
Date: Mon, 09 Feb 2009 10:43:57 -0600	[thread overview]
Message-ID: <49905D4D.30704@gmail.com> (raw)
In-Reply-To: <20090207093854.167c3221@krikkit>

Neil Bothwick wrote:
> On Fri, 06 Feb 2009 10:57:58 -0600, Chris Lieb wrote:
>
>> I don't want to do UnionFS since that requires me to patch the kernel,
>> which is more work than I have the time for.
>
> cd /usr/src/linux
> patch -p1 </path/to/patchfile
>
> You must be *really* short of time ;-)

My concern is more about making my own ebuild (based off of
gentoo-sources) that will patch the kernel source for me so that I can
easily distribute this patched kernel source to all of my computers.  I
need the process to be easy so that whom ever succeeds me doesn't have
to learn much more than just running a couple of scripts that I wrote.
Even how, I catch enough crap from my boss already for spending so much
time tinkering with servers instead of programming :)

A quick look at the gentoo-sources ebuild makes it look like the
patching must be happening in an eclass somewhere, but I'm no bash or
ebuild/eclass guru.  My skills end at fixing dependencies in packages
and doing simple ebuild copy version bumps.

Is there a guide out there for rolling my own kernel ebuild?

Chris

PS. Sorry if this is a double post.  The ml seems to silently reject my
posts that I do through gmane.




  reply	other threads:[~2009-02-09 16:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-06  4:16 [gentoo-user] Using portage through NFS Chris Lieb
2009-02-06 13:11 ` Mike Kazantsev
2009-02-06 16:57 ` [gentoo-user] " Chris Lieb
2009-02-07  9:38   ` Neil Bothwick
2009-02-09 16:43     ` Chris Lieb [this message]
2009-02-09 23:59       ` Roy Wright

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=49905D4D.30704@gmail.com \
    --to=chris.lieb@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