From: Trevor Woerner <twoerner@gmail.com>
To: Mike Looijmans <mike.looijmans@topic.nl>,
openembedded-core@lists.openembedded.org
Subject: Re: Using CRDA in combination with MDEV
Date: Mon, 20 Apr 2015 11:32:55 -0400 [thread overview]
Message-ID: <55351C27.70600@gmail.com> (raw)
In-Reply-To: <5530F9E0.6050906@topic.nl>
On 15-04-17 08:17 AM, Mike Looijmans wrote:
> I noticed there's a "crda" package in OE, but it RDEPENDS on udev for
> no other reason than simply because it provides a rules file for that.
> And I want to keep using mdev.
>
> I think it would be better to split this package, and have a
> "crda-udev" package that provides the rules file and the dependency on
> udev. Alternative is to have a PACKAGECONFIG to enable udev support.
I think the PACKAGECONFIG option would cause fewer surprises (perhaps?).
Otherwise anyone currently using the crda package with udev will now
have to change a previously-working build (to add the new crda-udev
package) so it can continue working. Is it possible to have the
crda-udev package automatically selected if udev is a distro feature and
the crda package is part of the image?
prev parent reply other threads:[~2015-04-20 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 12:17 Using CRDA in combination with MDEV Mike Looijmans
2015-04-20 15:32 ` Trevor Woerner [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=55351C27.70600@gmail.com \
--to=twoerner@gmail.com \
--cc=mike.looijmans@topic.nl \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox