orbea <or...@riseup.net> writes:

> On Mon, 11 Sep 2023 22:50:13 +0100
> Sam James <s...@gentoo.org> wrote:
>
>> orbea <or...@riseup.net> writes:
>> 
>> > On Mon, 11 Sep 2023 22:21:21 +0100
>> > Sam James <s...@gentoo.org> wrote:
>> >  
>> >> orbea <or...@riseup.net> writes:
>> >>   
>> >> > On Mon, 11 Sep 2023 21:31:30 +0100
>> >> > Sam James <s...@gentoo.org> wrote:
>> >> >    
>> >> >> Dale <rdalek1...@gmail.com> writes:
>> >> >>     
>> >> >> > orbea wrote:      
>> >> >> >> On Mon, 11 Sep 2023 17:29:47 +0200
>> >> >> >> "Andreas K. Huettel" <dilfri...@gentoo.org> 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.
>> >> 
>> >> Also note that the PR is a hack rather than a full implementation
>> >> of the functionality anyway, which may lead to runtime
>> >> misbehaviour.  
>> >
>> > According to upstream it implement's systemd's fallback path as
>> > explained in this comment.
>> >
>> > https://github.com/eudev-project/eudev/issues/249#issuecomment-1675520914
>> >  
>> 
>> That same comment goes on to say it's the "quick-n-dirty" fix and may
>> break applications.
>
> Slibtool also has no-op compatibility fixes that potentially could
> cause issues too, I don't see this being a problem there. If eudev was
> entirely broken or not being used I could understand why to remove it,
> but rather this is removing software that mostly works and is being
> used. With all due honesty is very disappointing to see this, I started
> to use Gentoo because it offered choices.

"mostly works" is generally not a great thing we want to
endorse.

slibtool is also a complete rewrite of libtool rather than a fork
which is out of date and missing features that consumers start
to expect from development. We also, importantly, don't drag in
slibtool on user systems unless they explicitly request it
and it doesn't wrongly satisfy dependencies on libtool itself.

Someone being disappointed doesn't get work done.

>
>> 
>> >
>> > However its fully possible to use Gentoo without requiring
>> > sticky-tags so I don't really see the urgency that requires
>> > removing software that has users that find it works for them. We
>> > even have the most recent upstream release which came out only a
>> > few months ago. 
>> >>   
>> >> >    
>> >> >>     
>> >> >> >
>> >> >> > Dale
>> >> >> >
>> >> >> > :-)  :-)       
>> >> >> 
>> >> >>     
>> >> 
>> >>   
>> 
>> 


Reply via email to