From: "Marty E. Plummer" <hanetzer@startmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Idea for a new project: gentoo-libs
Date: Sat, 23 Jun 2018 02:30:32 -0500 [thread overview]
Message-ID: <20180623073030.wdrjfrcv3swqwfkx@proprietary-killer> (raw)
In-Reply-To: <1529738520.21177.5.camel@gentoo.org>
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.
next prev parent reply other threads:[~2018-06-23 7:31 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-23 2:50 [gentoo-dev] Idea for a new project: gentoo-libs Marty E. Plummer
2018-06-23 2:57 ` Marty E. Plummer
2018-06-23 13:05 ` Jonas Stein
2018-08-05 16:55 ` Richard Yao
2018-06-23 7:22 ` Michał Górny
2018-06-23 7:30 ` Marty E. Plummer [this message]
2018-06-23 7:37 ` Michał Górny
2018-06-23 10:59 ` Alec Warner
2018-08-05 16:45 ` Richard Yao
2018-08-05 17:01 ` Alec Warner
2018-08-05 17:16 ` M. J. Everitt
2018-08-05 17:24 ` Rich Freeman
2018-08-05 17:31 ` M. J. Everitt
2018-08-05 18:12 ` Richard Yao
2018-08-05 18:35 ` Rich Freeman
2018-08-05 20:49 ` Richard Yao
2018-08-05 18:06 ` Richard Yao
2018-06-23 7:43 ` Mikle Kolyada
2018-06-23 8:15 ` Paweł Hajdan, Jr.
2018-06-23 8:55 ` Marty E. Plummer
2018-06-23 11:06 ` Roy Bamford
2018-06-23 23:52 ` Kent Fredric
2018-06-25 5:59 ` Hanno Böck
2018-06-27 0:03 ` Marty E. Plummer
2018-08-04 8:43 ` mcrypt status (Re: [gentoo-dev] Idea for a new project: gentoo-libs) Andrew Savchenko
2018-08-04 9:51 ` [gentoo-dev] Re: mcrypt status Martin Vaeth
2018-08-04 10:22 ` Andrew Savchenko
2018-08-04 14:29 ` mcrypt status (Re: [gentoo-dev] Idea for a new project: gentoo-libs) Hanno Böck
2018-08-04 15:25 ` Thomas Deutschmann
2018-08-05 4:57 ` Andrew Savchenko
2018-08-04 18:05 ` Marty E. Plummer
2018-08-04 19:22 ` Andrew Savchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180623073030.wdrjfrcv3swqwfkx@proprietary-killer \
--to=hanetzer@startmail.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox