Alexey Sokolov <[email protected]> writes:
> 11.09.2023 22:21, Sam James пишет: >> orbea <[email protected]> writes: >> >>> On Mon, 11 Sep 2023 21:31:30 +0100 >>> Sam James <[email protected]> wrote: >>> >>>> Dale <[email protected]> writes: >>>> >>>>> orbea wrote: >>>>>> On Mon, 11 Sep 2023 17:29:47 +0200 >>>>>> "Andreas K. Huettel" <[email protected]> wrote: >>>>>> >>>>>>> Am Montag, 11. September 2023, 17:22:43 CEST schrieb orbea: >>>>>>> >>>>>>>> Upstream is maintained still. >>>>>>>> >>>>>>>> https://github.com/eudev-project/eudev >>>>>>>> >>>>>>> No, it's not. >>>>>>> >>>>>>> >>>>>> Based on what? It has several commits this year and is currently >>>>>> working on both of my systems. Is there something specific showing >>>>>> why its not maintained? >>>>>> >>>>>> . >>>>>> >>>>> >>>>> On the link above it says this: >>>>> >>>>> >>>>> On 2021-08-20 Gentoo decided to abandon eudev and a new project was >>>>> established on 2021-09-14 by Alpine, Devuan and Gentoo contributors >>>>> (alphabetical order). >>>>> >>>>> >>>>> It seems to have a upstream that is active but no one is >>>>> maintaining it on Gentoo. Basically, it needs a Gentoo maintainer >>>>> now. It would seem given the time span that no one wants to take >>>>> it. >>>>> >>>>> Like others, I use it but didn't know it wasn't maintained anymore. >>>>> I hope someone will step up but if not, looks like we have to use >>>>> udev. >>>> >>>> No, see the linked bugs. Someone has to actually make it compatible >>>> with the tags API which software is starting to use. >>> >>> I think its only a matter of time. >>> >>> https://github.com/eudev-project/eudev/pull/253 >>> >>> I'll apply the patch and test the builds if it helps, but I don't know >>> about testing the runtime functionality of libgudev. >> Someone has to then bother reviewing it, merging it, releasing it, >> and >> ideally updating eudev for other stuff like this. > > Of course. Just like any other PR to any other project :) What's your point? I don't know what you mean. My point is none of that has been happening. > >> Also note that the PR is a hack rather than a full implementation >> of the functionality anyway, which may lead to runtime misbehaviour. > > And that's fine for programs which don't make use of the new API. > and? Someone has to actually check that?
