-
Notifications
You must be signed in to change notification settings - Fork 2.5k
[WIP] new package: libudev-zero #42488
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
You have quite a project in your hands :) |
It is waaaay too early for this, but I think
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. |
|
@mobinmob thanks, I rebased on your pr for now. |
b32cfd9 to
9c9c761
Compare
From the project homepage: Drop-in replacement for libudev intended to work with any device manager |
Yes, that is the goal and the developer has done trully amazing work. Last time I checked it did not implement all the libudev api, so as far as that is concerned it has not yet reached that goal. |
dfa6296 to
1349945
Compare
|
how about void-linux/void-runit#106 ? |
|
Here's a puzzle: why do some packages (e.g. wlroots libinput) both run_depends on eudev-libudev and shlib-requires libudev.so.1? if they only did the latter, then the provides/conflicts in libudev-zero should be enough.. |
|
btw, tinyramfs is now in the repo; it needs hostonly for now, but we can experiment more :) |
e7aa110 to
29f1e5e
Compare
a74f61f to
d5c9342
Compare
|
rebuilt wlroots successfully, while libinput (due to libblkid) fails :) |
Done, thanks! |
|
Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it. |
|
Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it. |
|
Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it. |
|
libudev-zero confirmed working with Pipewire through a small patch to libudev-zero: illiliti/libudev-zero#69 What is blocking this one from being packaged? |
|
@dkwo this is an unrelated question, do you know how to create a busybox based Void install? You seem interested in the GNUless linux landscape of things |
|
the package per se should be ok. maybe wait until they merge that patch and tag a new release? (don't know much about busybox, but i've been playing with dinit, and i like it. it's also packaged, but not as init for now. |
|
I didn't find the chimera community welcoming, at all. And I was also looking for a more Unix approach to Linux distros... Think I will stick to Alpine, nBSD and Void (in that order). |
|
Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it. |
|
Any updates on this? |
|
You need to provide your own alternative to udevd, e.g. mdevd (change init scripts, provide a service and config for mdevd). Maybe there's a better way to deal with conflicts/replaces. (E.g. in Alpine apk a package can depend on libudev.so.1 cleanly, and then they'd use in the libudev-zero package.) Just not sure if this can be achieved in xbps at present. |
|
At this time, we aren't interested in supporting alternative udev implementations on Void. |
https://github.com/illiliti/libudev-zero