From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 00/12 v8] Introduce libudev (branch yem/libudev-4)
Date: Wed, 27 Jul 2016 23:37:56 +0200 [thread overview]
Message-ID: <87twfawymj.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20160718175241.GA3738@free.fr> (Yann E. MORIN's message of "Mon, 18 Jul 2016 19:52:41 +0200")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
Hi Yann,
>> So I'm not sure if it's really worth the effort. After all, installing
>> only libudev without eudev is not really supported upstream (we have to
>> trick by building only some subdirectories).
>>
>> I'm not entirely decided yet, so I'm waiting for arguments. But I'm
>> hesitating between merging this, or asking people who really care about
>> this to simply remove the eudev daemon in a post-build script.
> But then you would not have libudev if you use mdev or a static /dev.
Is that a common use case? I wouldn't expect anybody to use static /dev
any more, and if you are using mdev then that is presumably for running
scripts on hotplug events? If so, why not just use the udev daemon for
this?
I do understand this could be useful for using libudev with devtmpfs
/dev, but wouldn't a simple post-build script to rm S10udev + udevd get
us 90% of the way without any extra complexity?
--
Venlig hilsen,
Peter Korsgaard
next prev parent reply other threads:[~2016-07-27 21:37 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 22:16 [Buildroot] [PATCH 00/12 v8] Introduce libudev (branch yem/libudev-4) Yann E. MORIN
2016-07-11 22:16 ` [Buildroot] [PATCH 01/12 v8] package/eudev: explicitly disable rules generator if not wanted Yann E. MORIN
2016-07-15 18:36 ` Thomas Petazzoni
2016-07-11 22:16 ` [Buildroot] [PATCH 02/12 v8] package/eudev: use the description on their home page Yann E. MORIN
2016-07-15 18:36 ` Thomas Petazzoni
2016-07-11 22:16 ` [Buildroot] [PATCH 03/12 v8] package/eudev: add option to enable the udev daemon Yann E. MORIN
2016-07-11 22:16 ` [Buildroot] [PATCH 04/12 v8] package/eudev: fix configure options Yann E. MORIN
2016-07-15 18:36 ` Thomas Petazzoni
2016-07-11 22:16 ` [Buildroot] [PATCH 05/12 v8] package/eudev: libgudev is no longer provided by eudev Yann E. MORIN
2016-07-15 18:36 ` Thomas Petazzoni
2016-07-11 22:16 ` [Buildroot] [PATCH 06/12 v8] package/eudev: allow building only libudev Yann E. MORIN
2016-07-13 19:40 ` Bernd Kuhls
2016-07-11 22:16 ` [Buildroot] [PATCH 07/12 v8] package/libudev: new virtual package Yann E. MORIN
2016-07-13 19:41 ` Bernd Kuhls
2016-07-11 22:16 ` [Buildroot] [PATCH 08/12 v8] package/eudev: provides libudev Yann E. MORIN
2016-07-13 19:41 ` Bernd Kuhls
2016-07-11 22:16 ` [Buildroot] [PATCH 09/12 v8] package/systemd: " Yann E. MORIN
2016-07-11 22:16 ` [Buildroot] [PATCH 10/12 v8] package/libudev: make it selectable Yann E. MORIN
2016-07-13 19:41 ` Bernd Kuhls
2016-07-11 22:16 ` [Buildroot] [PATCH 11/12 v8] package/qt5base: optionally use libudev Yann E. MORIN
2016-07-11 22:16 ` [Buildroot] [PATCH 12/12 v8] package/libinput: only needs libudev, not udev daemon Yann E. MORIN
2016-07-12 20:16 ` [Buildroot] [PATCH 00/12 v8] Introduce libudev (branch yem/libudev-4) Bernd Kuhls
2016-07-12 20:49 ` Yann E. MORIN
2016-07-13 19:43 ` Bernd Kuhls
2016-07-16 13:47 ` Thomas Petazzoni
2016-07-18 17:52 ` Yann E. MORIN
2016-07-18 20:19 ` Thomas Petazzoni
2016-07-27 21:37 ` Peter Korsgaard [this message]
2016-07-28 20:01 ` Bernd Kuhls
2016-07-28 20:28 ` Peter Korsgaard
2021-03-08 21:59 ` Bernd Kuhls
[not found] ` <99d32ded-9102-c9a7-4f15-38d1bd0a0537@t-online.de>
2021-03-08 22:30 ` Yann E. MORIN
2021-08-13 5:28 ` Bernd Kuhls
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=87twfawymj.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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