> looking at Debian bug 735275 > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735275 > > and the wide impact it has on upstream (nodejs, webkit, chrome etc. are > affected by the bump to libudev.1) I'd rather keep libudev.0 around as > a vdev patched version, would that be possible?
Thanks for the link. A lot more programs depend on libudev.1 than libudev.0. I need to figure out the difference between them. If it's just what the DD said (i.e. a few symbols got removed), I might be able to patch them back in and have libudev-compat serve as a drop-in replacement for libudev.0 and libudev.1. I don't know what the full extent of the differences are, though--if the semantics of the API changed, then it will be more challenging. -Jude On Tue, Mar 24, 2015 at 6:44 AM, Jaromil <[email protected]> wrote: > > moreover on libudev > > looking at Debian bug 735275 > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735275 > > and the wide impact it has on upstream (nodejs, webkit, chrome etc. are > affected by the bump to libudev.1) I'd rather keep libudev.0 around as > a vdev patched version, would that be possible? > > I understand this would gain Devuan even more backward compatibility > with upstream distributed binaries. > > ciao > > >
_______________________________________________ Dng mailing list [email protected] https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
