From: mobinmob <mobinmob@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [rfc] udev alternatives
Date: Mon, 27 Feb 2023 18:38:04 +0100 [thread overview]
Message-ID: <20230227173804.ShWLBORlEsYGkSLqzLo6KYz74ra3jAR31RjD0Z7w8mI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42488@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 828 bytes --]
New comment by mobinmob on void-packages repository
https://github.com/void-linux/void-packages/pull/42488#issuecomment-1446758416
Comment:
> * how to deal with eudev-libudev: libudev-zero replaces, conflicts, provides it? it provides /usr/lib/libudev.so.1, I expect some stuff built with eudev-libudev-devel (wlroots, libinput) to work with it, while other may not if one removes eudev-libudev (lvm2, pipewire), see https://github.com/illiliti/libudev-zero
It is **waaaay** too early for this, but I think `replaces` is the wrong choice here.
> * find an optimal mdev.conf (current one is taken from kiss-linux, alpine has a similar one)
That is not the only thing you need. You should look at the mdev-like-a-boss scripts and work with them and also checkout how you can extend the functionality in other ways.
next prev parent reply other threads:[~2023-02-27 17:38 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 16:49 [PR PATCH] " dkwo
2023-02-27 17:10 ` mobinmob
2023-02-27 17:11 ` mobinmob
2023-02-27 17:31 ` mobinmob
2023-02-27 17:38 ` mobinmob [this message]
2023-02-27 17:38 ` mobinmob
2023-02-27 18:05 ` [PR PATCH] [Updated] " dkwo
2023-02-27 18:06 ` dkwo
2023-02-27 18:07 ` [PR PATCH] [Updated] " dkwo
2023-02-27 18:25 ` dkwo
2023-02-27 18:38 ` dkwo
2023-02-27 21:25 ` dkwo
2023-02-27 23:04 ` [PR PATCH] [Updated] " dkwo
2023-02-28 15:20 ` mobinmob
2023-02-28 15:20 ` mobinmob
2023-02-28 17:19 ` mobinmob
2023-02-28 18:40 ` [PR PATCH] [Updated] " dkwo
2023-02-28 18:45 ` dkwo
2023-02-28 21:03 ` dkwo
2023-03-01 19:57 ` dkwo
2023-03-01 20:55 ` new package: libudev-zero dkwo
2023-03-01 22:09 ` [PR PATCH] [Updated] " dkwo
2023-03-01 23:07 ` dkwo
2023-03-06 19:24 ` [PR PATCH] [Updated] " dkwo
2023-04-07 14:32 ` dkwo
2023-04-11 20:34 ` [PR PATCH] [Updated] " dkwo
2023-04-11 20:35 ` dkwo
2023-04-11 21:49 ` dkwo
2023-04-21 21:34 ` dkwo
2023-04-24 18:24 ` dkwo
2023-04-26 14:11 ` dkwo
2023-04-26 14:19 ` dkwo
2023-04-26 17:41 ` mobinmob
2023-04-26 17:42 ` mobinmob
2023-04-29 15:09 ` [PR PATCH] [Updated] [WIP] " dkwo
2023-04-29 15:17 ` dkwo
2023-05-01 9:06 ` mobinmob
2023-05-01 14:43 ` [PR PATCH] [Updated] " dkwo
2023-07-15 21:56 ` dkwo
2023-10-14 1:44 ` github-actions
2023-10-15 21:44 ` [PR PATCH] [Updated] " dkwo
2024-01-14 1:50 ` github-actions
2024-01-14 10:39 ` [PR PATCH] [Updated] " dkwo
2024-04-14 1:59 ` github-actions
2024-04-15 17:08 ` [PR PATCH] [Updated] " dkwo
2024-04-16 23:33 ` xplshn
2024-04-16 23:34 ` xplshn
2024-04-16 23:35 ` xplshn
2024-04-17 13:46 ` dkwo
2024-04-18 0:47 ` xplshn
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=20230227173804.ShWLBORlEsYGkSLqzLo6KYz74ra3jAR31RjD0Z7w8mI@z \
--to=mobinmob@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).