public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Progress on s/udev/mdev/
Date: Mon, 21 Nov 2011 17:34:29 +0700	[thread overview]
Message-ID: <CAA2qdGXWWVbDyOayeOXn3RnVVnMDVqmXOJCPM0QW4vaXvFoS-Q@mail.gmail.com> (raw)
In-Reply-To: <20111121102222.GB7461@waltdnes.org>

On Mon, Nov 21, 2011 at 17:22,  <waltdnes@waltdnes.org> wrote:
> On Sat, Nov 19, 2011 at 09:53:50PM -0600, Dale wrote
>
>> Question:  Is this going to be added to the shiney new Gentoo wiki at
>> some point?  The wiki needs some more content for sure.  ;-)
>>
>> I didn't know if ya'll had thought of this before or not.
>
>  Actually, I was hoping to convince the devs to accept a patched ebuild
> that would accept busybox with the +mdev flag, in addition to the other
> options in RDEPEND.  If this gets accepted by the devs, it would imply
> changes in the Gentoo docs, plus an additional new profile, etc, etc.
>

True, it would be very preferred to have mdev as a new profile.

BUT ... If the procedure lacks something and/or causes a huge number
of bugs/annoyances, it will never be accepted as a profile.

So we'll have to start with what we have right now, and push it to as
many early adopters as possible. One way is to put this into wiki.g.o
as an article, and give people a linkback via this list and/or the
forums.

>  Right now, it has to be manually maintained, because it's off the
> beaten path, and beta-testing, etc.  I'm not looking to fork Gentoo.  I
> want this to become another optional profile, not a hack-job that has to
> be manually maintained by the user.
>

Eh? The changes are so minor it truly can't be considered a fork.

Hack-job, perhaps. Fork, no ;-)

>  IANACP (I Am Not A C Programmer).  I'm willing to help out in the
> documentation, or where ever else I can.
>

AFAICT, your procedure involves no C programming at all.

After reflecting on your procedure, I think the whole process can be
automated via scripts (bash and/or .ebuild).

Let's see if I can whup up such a script within this week...

Rgds,
-- 
FdS Pandu E Poluan
~ IT Optimizer ~

 • LOPSA Member #15248
 • Blog : http://pepoluan.tumblr.com
 • Linked-In : http://id.linkedin.com/in/pepoluan



      reply	other threads:[~2011-11-21 10:36 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
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 [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=CAA2qdGXWWVbDyOayeOXn3RnVVnMDVqmXOJCPM0QW4vaXvFoS-Q@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