From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@uclibc.org
Subject: Re: [Buildroot] [PATCH/next v9 00/12] Introduce libudev (branch yem/libudev-6)
Date: Fri, 25 Aug 2023 19:05:32 +0200 [thread overview]
Message-ID: <20230825190532.43dfeb9b@windsurf> (raw)
In-Reply-To: <pan$e13d2$de8bbe61$f0a8808c$96f93b15@ID-313208.user.individual.net>
Hello Bernd,
On Fri, 25 Aug 2023 18:24:41 +0200
Bernd Kuhls <bernd@kuhls.net> wrote:
> the reason I am carrying this patch in my personal tree is maintenance of
> a buildroot-based system which uses
>
> BR2_ROOTFS_DEVICE_CREATION_STATIC=y
>
> Without the libudev series I can not use packages like Kodi, and no, I can
> not change the rootfs setting for this system, sorry.
So you can apply complicated patches/changes, but you cannot adjust the
configuration of your system to use eudev? This does not really sound
like a very good/solid argument in favor of this patch series :-/
Especially when you have Kodi, the size difference between "just
libudev" and "libudev + eudev" is insignificant compared to the size of
Kodi.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-08-25 17:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-06 14:02 [Buildroot] [PATCH/next v9 00/12] Introduce libudev (branch yem/libudev-6) Bernd Kuhls
2023-08-06 14:02 ` [Buildroot] [PATCH/next v9 01/12] package/eudev: add option to enable the udev daemon Bernd Kuhls
2023-08-06 14:02 ` [Buildroot] [PATCH/next v9 02/12] package/eudev: allow building only the library Bernd Kuhls
2023-08-06 14:02 ` [Buildroot] [PATCH/next v9 03/12] package/libudev: new virtual package Bernd Kuhls
2023-08-06 14:02 ` [Buildroot] [PATCH/next v9 04/12] package/eudev: provides libudev Bernd Kuhls
2023-08-06 14:02 ` [Buildroot] [PATCH/next v9 05/12] package/systemd: " Bernd Kuhls
2023-08-06 14:02 ` [Buildroot] [PATCH/next v9 06/12] package/libudev: make it selectable Bernd Kuhls
2023-08-06 14:02 ` [Buildroot] [PATCH/next v9 07/12] package/qt5base: optionally use libudev Bernd Kuhls
2023-08-06 14:02 ` [Buildroot] [PATCH/next v9 08/12] package/libinput: only needs libudev, not udev daemon Bernd Kuhls
2023-08-06 14:02 ` [Buildroot] [PATCH/next v9 09/12] package/kodi: " Bernd Kuhls
2023-08-06 14:02 ` [Buildroot] [PATCH/next v9 10/12] package/libv4l: optionally use libudev Bernd Kuhls
2023-08-06 14:02 ` [Buildroot] [PATCH/next v9 11/12] package/libcec: " Bernd Kuhls
2023-08-06 14:02 ` [Buildroot] [PATCH/next v9 12/12] package/usbutils: only needs libudev, not udev daemon Bernd Kuhls
2023-08-22 20:59 ` [Buildroot] [PATCH/next v9 00/12] Introduce libudev (branch yem/libudev-6) Thomas Petazzoni via buildroot
[not found] ` <20230822225949.2b326664__48539.150941518$1692738023$gmane$org@windsurf>
2023-08-25 16:24 ` Bernd Kuhls
2023-08-25 17:05 ` Thomas Petazzoni via buildroot [this message]
2023-08-25 17:22 ` 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=20230825190532.43dfeb9b@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=buildroot@uclibc.org \
--cc=thomas.petazzoni@bootlin.com \
/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