From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Progress on s/udev/mdev/
Date: Sat, 19 Nov 2011 12:21:10 +0700 [thread overview]
Message-ID: <CAA2qdGXXk24cHfob4n4THxV0_o4fBVtNJ9K2f+B1Yk_bQJ8UwA@mail.gmail.com> (raw)
In-Reply-To: <20111119045539.GA8261@waltdnes.org>
[-- Attachment #1: Type: text/plain, Size: 928 bytes --]
On Nov 19, 2011 11:58 AM, <waltdnes@waltdnes.org> wrote:
>
> On Sat, Nov 19, 2011 at 08:41:43AM +0700, Pandu Poluan wrote
> > On Nov 19, 2011 6:56 AM, "Neil Bothwick" <neil@digimed.co.uk> wrote:
> > >
> > > On Sat, 19 Nov 2011 09:38:42 +1100, Paul Colquhoun wrote:
> > >
> > > > You can copy the ebuild to your own private overlay
> > > > ( /usr/local/portage ) make your changes there, and bump the version
> > > > number slightly.
> > >
> > > No need to bump the version number, overlays take priority over the
> > > standard tree when there are equal version numbers.
> > >
> >
> > I knew I forgot something so simple >.<
> >
> > Thanks!
> >
> > Hmmm... so, @waltdnes, you should modify the procedure a bit, there...
>
> Will do. This is what beta tests are for <G>.
>
Great! BTW, if the ebuild goes into overlay, it could use a newer EAPI,
couldn't it?
If it could, then it'll solve the problem of busybox[mdev].
Rgds,
[-- Attachment #2: Type: text/html, Size: 1362 bytes --]
next prev parent reply other threads:[~2011-11-19 5:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 11:33 [gentoo-user] Progress on s/udev/mdev/ Pandu Poluan
2011-11-18 22:38 ` Paul Colquhoun
2011-11-18 23:53 ` Neil Bothwick
2011-11-19 1:41 ` Pandu Poluan
2011-11-19 4:55 ` waltdnes
2011-11-19 5:21 ` Pandu Poluan [this message]
2011-11-20 2:24 ` [gentoo-user] " Steven J Long
2011-11-20 3:24 ` [gentoo-user] " Pandu Poluan
2011-11-20 3:53 ` Dale
2011-11-20 4:33 ` Pandu Poluan
2011-11-21 10:22 ` waltdnes
2011-11-21 10:34 ` Pandu Poluan
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=CAA2qdGXXk24cHfob4n4THxV0_o4fBVtNJ9K2f+B1Yk_bQJ8UwA@mail.gmail.com \
--to=pandu@poluan.info \
--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