W dniu sob, 23.06.2018 o godzinie 02∶30 -0500, użytkownik Marty E. Plummer napisał: > On Sat, Jun 23, 2018 at 09:22:00AM +0200, Michał Górny wrote: > > W dniu pią, 22.06.2018 o godzinie 21∶50 -0500, użytkownik Marty E. > > Plummer napisał: > > > So, as you may be aware I've been doing some work on moving bzip2 to an > > > autotools based build. Recently I've ran into app-crypt/mhash, which is > > > in a semi-abandoned state (talking with the maintainer on twitter atm), > > > and I was thinking it may be a good idea to set up a project for keeping > > > these semi-abandoned and really-abandoned libraries and projects up to > > > date and such. > > > > > > Basically, an upstream for packages who's upstream is either > > > uncontactable or is otherwise not accepting bug fixes and patches. So > > > far I can only think of app-crypt/mhash and app-arch/bzip2 but I'm sure > > > there are others in this state. > > > > > > > So in order to fix problem of semi-abandoned packages, you're creating > > an indirect herd-like entity that will soon be semi-abandoned itself > > because people will be dumping random packages into it and afterwards > > nobody will claim responsibility for them. > > > > -- > > Best regards, > > Michał Górny > > No, I mean for packages which are important enough in gentoo to warrant > such treatment. For instance, every email I've tried for bzip2's > upstream bounced or recieved no reply. That, I assume, is important > enough to actually maintain and improve. Any other library which may be > as important which are as inactive would be added.
Sounds like you're going to take over half of base-system ;-). I really prefer having single dedicated individuals for that kind of stuff. Projects just blur the responsibility. -- Best regards, Michał Górny
signature.asc
Description: This is a digitally signed message part
