From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package: udev is now provided by systemd or eudev.
Date: Tue, 17 Sep 2013 20:45:39 +0200 [thread overview]
Message-ID: <20130917204539.7c788c2b@skate> (raw)
In-Reply-To: <20130917125352.GB13723@pc-eric>
Dear Eric Le Bihan,
On Tue, 17 Sep 2013 14:53:52 +0200, Eric Le Bihan wrote:
> > (1) All the existing BR2_PACKAGE_UDEV* options are being renamed,
> > without them being added in Config.in.legacy to provide a smooth
> > migration path for users upgrading Buildroot. I believe this should be
> > fixed by migrating them to eudev automatically through
> > Config.in.legacy logic.
> I was not aware of this mechanism, as I was previously working with an old
> version of Buildroot (2012.08).
No problem.
> As mentioned in my reply to Arnout, I think it is better to have the selection
> of the init system before the selection of the /dev management, because the
> first item to choose when building a system is how to start it, not how to
> manage the devices.
Well, that's a matter of taste, but why not :)
> Our constraints are:
>
> 1) we need to keep a virtual udev package to avoid breaking Pulseaudio, Weston,
> Udisks, etc: as eudev is identical to udev from systemd, it does not
> matter which one is selected to build these packages.
Right.
> 2) there is no need to offer a static /dev, mdev or eudev if systemd is
> selected. The opposite is allowed.
Sure.
> I ack the idea of moving the choice between udev (from systemd) and eudev to
> the "System Configuration" menu. So I suggest that, when the user selects
> the init system:
>
> - if systemd is selected, then the menu to select /dev management is *not*
> displayed, but replaced by a comment as "/dev management with udev
> (from systemd)". The virtual package udev is selected.
I don't think that the udev virtual package should have a Config.in
option to select. It should most likely be like the OpenGL virtual
package: it provides an invisible BR2_PACKAGE_HAS_UDEV, which gets
selected by both systemd and eudev. All packages that need an udev
implementation to be available will have to 'depends on
BR2_PACKAGE_HAS_UDEV' and to do FOO_DEPENDENCIES += udev.
> - if systemd is not selected, then the menu to select /dev management is
> displayed, with the following choices:
>
> * static /dev
> * /dev with devtmpfs
> * /dev with devtmpfs + mdev
> * /dev with devtmpfs + eudev
Right.
> Selecting eudev selects the udev virtual package.
See above. I don't think udev should have a Config.in option to be
selected.
> The user can configure
> the extras for eudev in the appropriate "Target packages" section.
Right.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-09-17 18:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-06 14:01 [Buildroot] [PATCH 1/1] package: udev is now provided by systemd or eudev eric.le.bihan.dev at free.fr
2013-09-06 14:08 ` Eric Le Bihan
2013-09-10 20:24 ` Arnout Vandecappelle
2013-09-17 10:40 ` Eric Le Bihan
2013-09-18 4:45 ` Thomas Petazzoni
2013-09-18 6:52 ` Arnout Vandecappelle
2013-09-17 18:37 ` Thomas Petazzoni
2013-09-18 6:57 ` Arnout Vandecappelle
2013-09-18 15:56 ` Thomas Petazzoni
2013-09-18 16:04 ` Arnout Vandecappelle
2013-09-18 16:40 ` Thomas Petazzoni
2013-09-18 21:46 ` Arnout Vandecappelle
2013-09-17 5:17 ` Thomas Petazzoni
2013-09-17 12:53 ` Eric Le Bihan
2013-09-17 18:45 ` Thomas Petazzoni [this message]
2013-09-18 7:00 ` Arnout Vandecappelle
2013-09-18 15:58 ` Thomas Petazzoni
2013-09-18 16:06 ` Arnout Vandecappelle
2013-09-18 16:41 ` Thomas Petazzoni
2013-09-18 17:34 ` Sagaert Johan
2013-09-18 17:39 ` Thomas Petazzoni
2013-09-18 18:13 ` Sagaert Johan
2013-09-18 18:05 ` [Buildroot] [PATCH 1/1] package: udev is now provided bysystemd " Sagaert Johan
2013-09-18 18:16 ` Thomas Petazzoni
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=20130917204539.7c788c2b@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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