public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] rfc: glibc versions prior to 2.19-r1
Date: Mon, 22 Dec 2014 12:47:00 -0500	[thread overview]
Message-ID: <CAGfcS_keuw-5N86e6izZWaJHN=m8phVXJM_oFi6NrVNCaWATNw@mail.gmail.com> (raw)
In-Reply-To: <54983E36.3090400@gentoo.org>

On Mon, Dec 22, 2014 at 10:52 AM, Anthony G. Basile <blueness@gentoo.org> wrote:
> On 12/22/14 10:39, Rich Freeman wrote:
>>
>> On Mon, Dec 22, 2014 at 10:04 AM, William Hubbs <williamh@gentoo.org>
>> wrote:
>>>
>>> On Mon, Dec 22, 2014 at 03:18:01PM +0100, Matthias Maier wrote:
>>>>
>>>> IMHO, maintaining a sensible set of old glibc versions of the last 5
>>>> years makes sense, and we should try to support it:
>>>
>>> We have a general policy in the distro that says we only have to worry
>>> about one year. Besides that, linux-2.6.32, which is the oldest kernel
>>> glibc-2.20 will support was released in 2009, so I think it is
>>> reasonable to drop the old glibc versions.
>>>
>> I think a general policy like this makes sense.  Nothing prevents a
>> maintainer from keeping around stuff longer, but that should be up to
>> them (and issues in old versions shouldn't be the responsibility of
>> others to clean up if they are blockers - just move forward and let
>> things break after a warning or treeclean if the problem is really
>> serious).
>
>
> Please let's not "tidy up" gentoo.  That "old" stuff is useful even if its
> not useful to those who don't see a use for it.  Let the maintainers decide
> if they want to put effort into keeping it around.
>

Wasn't that what I just said?  Maintainers decide what they want to
put effort into maintaining.  The only bit I added beyond what you
said is that if they DON'T maintain the old versions others don't have
to do it for them.  (ie, bugs against them don't count as blockers
towards other changes in the tree)  Treecleaning is only appropriate
if things are horribly broken, which is the usual policy.

--
Rich


      parent reply	other threads:[~2014-12-22 17:47 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-21 15:28 [gentoo-dev] rfc: glibc versions prior to 2.19-r1 William Hubbs
2014-12-21 19:26 ` Markos Chandras
2014-12-22  9:36   ` Sergey Popov
2014-12-22 12:50 ` Lars Wendler
2014-12-22 14:18   ` Matthias Maier
2014-12-22 15:04     ` William Hubbs
2014-12-22 15:39       ` Rich Freeman
2014-12-22 15:52         ` Anthony G. Basile
2014-12-22 16:11           ` Andreas K. Huettel
2014-12-22 16:20             ` Andrew Savchenko
2014-12-22 17:40               ` Anthony G. Basile
2014-12-22 17:55               ` Rich Freeman
2014-12-22 21:22               ` Andreas K. Huettel
2014-12-22 21:45                 ` Rich Freeman
2014-12-23  2:53                 ` Andrew Savchenko
2014-12-23  4:55                 ` William Hubbs
2014-12-23  8:10                   ` Matthias Maier
2014-12-23 15:51                     ` William Hubbs
2014-12-23 17:48                       ` Matthias Maier
2014-12-23 10:48                   ` Rich Freeman
2014-12-23 13:45                   ` Anthony G. Basile
2014-12-23 14:39                     ` William Hubbs
2014-12-23 14:46                       ` Anthony G. Basile
2014-12-23 16:23                         ` William Hubbs
2014-12-22 16:33             ` Matthias Maier
2014-12-22 17:24             ` Anthony G. Basile
2014-12-22 21:37               ` Andreas K. Huettel
2014-12-23 13:36                 ` Anthony G. Basile
2014-12-24  2:39                   ` [gentoo-dev] " Duncan
2014-12-24 12:14                     ` Anthony G. Basile
2014-12-24  2:40                   ` [gentoo-dev] " Matt Turner
2014-12-24 12:50                     ` Anthony G. Basile
2014-12-24 14:33                   ` Andreas K. Huettel
2014-12-25  0:28             ` Ben de Groot
2014-12-22 17:47           ` Rich Freeman [this message]

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='CAGfcS_keuw-5N86e6izZWaJHN=m8phVXJM_oFi6NrVNCaWATNw@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --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