From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] udev: Use udev.inc and add udevadm to udev pacakge instead of udev-utils
Date: Tue, 25 May 2010 07:50:55 -0700 [thread overview]
Message-ID: <20100525145055.GE26493@gmail.com> (raw)
In-Reply-To: <htftsf$ilt$1@dough.gmane.org>
On (25/05/10 09:22), Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 25-05-10 08:49, raj.khem@gmail.com wrote:
> > From: Khem Raj <raj.khem@gmail.com>
> >
> > * Main purpose of the patch was to fix the problem where udev-utils was
> > needed to be in root file system just to get udevadm binary. So this
> > binary is moved into udev package instead.
> >
> > * Use INC_PR
> >
> > * Use udev.inc in all recipes.
> >
> > * All udev recipes built udev_151 and udev_124 runs fine too.
>
> I explicitly didn't use udev.inc in udev 151 because it made the recipe
> very hard to read. It would make more sense to do a udev-1xx.inc based
> on udev 151 and use that for future recipes.
On the contrary I thought it was more confusing to include udev.inc in some
and not in others.I find that the recipes are quite similar. infact do_install function could
be also commonized properly and extra bits put into install_append in given
recipes. I did not spend time doing that yet.
Then the description field is also weirdly overridden in recipes probably
that needs fixing as well.
Any specific reason to have udev-1xx.inc ?
I will leave udev_151 as it is and only commit the udevadm change for now
-Khem
prev parent reply other threads:[~2010-05-25 14:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 6:49 [PATCH] udev: Use udev.inc and add udevadm to udev pacakge instead of udev-utils raj.khem
2010-05-25 7:22 ` Koen Kooi
2010-05-25 9:11 ` Grzegorz Toporek
2010-05-25 9:25 ` Koen Kooi
2010-05-25 10:04 ` Grzegorz Toporek
2010-05-25 9:55 ` Henri Bragge
2010-05-25 14:50 ` Khem Raj [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=20100525145055.GE26493@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.