Martijn BraamJun 3, 2023
*drops post* https://blog.brixit.nl/developers-are-lazy-thus-flatpak/
Developers are lazy, thus Flatpak

A look at Flatpak madness

BrixIT Blog
Show threadrazzeJun 3, 2023

@martijnbraam I agree, that usb stuff should get worked on, but I needed to install udev rules for normal packages too to work. So that part doesn't really make sense to me.

But no usb events is the real deal breaker for me right now (well I still use/maintain those packages)

Show threadMartijn BraamJun 3, 2023
@razze the nice thing with normal distributions is you can just package udev rules and it works automagically for end users. No such option with flatpak
Show threadrazze

@martijnbraam funny that that never seemed to work for me or packagers didn't do that then. But I only tried on manjaro (aur) and fedora.

I also thought udev rules wouldn't be needed, if you make that device known to systemd in the first place? At least I think that's what georges suggested.

Which means udev shouldn't be needed for flatpak to work.

Jun 4, 2023 at 12:31amWeb
Show threadMartijn BraamJun 4, 2023
@razze works fine, i have the openswitcher application that is packaged on Alpine and Debian and it ships some custom udev rules to allow plugdev users to access it. Systemd is not really relevant here unless they invented something new again
Show threadrazzeJun 4, 2023
@martijnbraam I think the idea is to add the device here https://github.com/systemd/systemd/tree/main/hwdb.d and if that's not possible something like this https://github.com/systemd/systemd/pull/22730
systemd/hwdb.d at main · systemd/systemd

The systemd System and Service Manager . Contribute to systemd/systemd development by creating an account on GitHub.

GitHub