public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Campbell <zlg@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Packages up for grabs due to retirement
Date: Thu, 5 Jan 2017 22:00:26 -0800	[thread overview]
Message-ID: <7a2010ad-185c-514a-c11f-7000b09e4ff5@gentoo.org> (raw)
In-Reply-To: <a6f653a5-f0dd-79ce-7171-262806151cc4@iee.org>


[-- Attachment #1.1: Type: text/plain, Size: 2989 bytes --]

On 01/03/2017 06:31 AM, M. J. Everitt wrote:
> On 03/01/17 11:05, Michał Górny wrote:
>> On Tue, 3 Jan 2017 16:00:52 +0700 (+07)
>> grozin@gentoo.org wrote:
>>
>>> On Mon, 2 Jan 2017, Brian Evans wrote:
>>>> IMO, this one should be given last-rites as upstream is dead and it
>>>> heavily depends on wireless-tools and WEXT.  
>>> I use it on 2 notebooks. It works fine, and is (from my point of view) the 
>>> most convenient tool to control ethernet and wifi connections on a 
>>> notebook. Why lastrite it when it works?
>> This is the Gentoo Way™. Having a working software is not a goal.
>> Gentoo focuses on the best bleeding edge experience and therefore
>> highly relies on software packages that are under active development
>> and require active maintenance. The packages in early stages of
>> development are especially interesting since they can supply users
>> and developers with variety of interesting bugs and unpredictable
>> issues.
>>
> From your response I infer the following, please discuss:
> 1) "working software is not a goal" .. so we can have a tree full of
> broken and/or unstable packages. What is the point of any QA/CI system
> if this is applicable?
> 2) "require active maintainance" .. by whom exactly? Where are the flood
> of keen developers bringing their bleeding edge code (with their
> ludicrous packaging requirements and language demands) to Gentoo?
> 3) "interesting bugs and unpredictable isssue" .. WTF?
> 
> Michal .. are you (once again...) High .. or is your email (once again)
> so soaked in sarcasm we can't tell any useful content from the complete
> drivel ...
> 
Maybe I'm weird but I thought it was funny...

I'm in favor of keeping software around until it breaks. When there's a
non-existent upstream and nobody's willing to take up the helm
themselves, it's a clear indication that it's in danger of being
treecleaned. In some cases that's good; some packages get left behind
and never updated, CVEs get released, nobody cares about the package and
it sits masked for a while. Those are the packages we should consider
for treecleaning, not just "oh it's been 2 years since a release" or
"upstream website troubles".

On the latter count, does anyone attempt to reach upstream before
suggesting we get rid of the package(s)? Is there not some forum we can
use to reach users who may be interested in proxy-maintaining it? This
discussion makes me wonder if we need (more) formal guidelines for
treecleaning. I think we've got a few people who are eager to clean the
tree -- and their goal is admirable -- but until we can get metrics on
who's using what, it's hard to say how much damage removing a package
will do for users. A thread on gentoo-user re: lastrites might not be a
bad idea.

Thanks for the laugh Michał. :)

-- 
Daniel Campbell - Gentoo Developer
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net
fpr: AE03 9064 AE00 053C 270C  1DE4 6F7A 9091 1EA0 55D6


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2017-01-06  6:00 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-31 21:54 [gentoo-dev] Packages up for grabs due to retirement Thomas Kahle
2016-12-31 23:00 ` James Le Cuirot
2017-01-01  9:42   ` Thomas Kahle
2017-01-01  9:54     ` James Le Cuirot
2017-01-01  9:48 ` [gentoo-dev] " David Seifert
2017-01-01 10:08   ` Thomas Kahle
2017-01-01 17:16 ` [gentoo-dev] " Lars Wendler
2017-01-02 19:53   ` Brian Evans
2017-01-03  9:00     ` grozin
2017-01-03 11:05       ` Michał Górny
2017-01-03 14:14         ` Why lastrite when it works? (Was: Re: [gentoo-dev] Packages up for grabs due to retirement) Michael Mol
2017-01-03 14:24           ` Damien LEVAC
2017-01-03 14:57             ` Michael Mol
2017-01-03 15:10               ` Kristian Fiskerstrand
2017-01-03 17:10                 ` Matthew Thode
2017-01-03 15:11               ` Damien LEVAC
2017-01-03 17:07                 ` Matthew Thode
2017-01-03 15:12               ` M. J. Everitt
2017-01-03 15:23               ` Rich Freeman
2017-01-03 15:41                 ` Alice Ferrazzi
2017-01-03 16:59                   ` james
2017-01-03 16:09                 ` Michael Mol
2017-01-03 16:29                   ` Rich Freeman
2017-01-06  4:27                 ` Kent Fredric
2017-01-06 14:13                   ` Michael Mol
2017-01-06 20:51                     ` William L. Thomson Jr.
2017-01-06 15:01                   ` Rich Freeman
2017-01-07  2:51                     ` M. J. Everitt
2017-01-06 17:14                   ` Alec Warner
2017-01-06 17:26                     ` Rich Freeman
2017-01-06 20:46                     ` William L. Thomson Jr.
2017-01-17 12:45                       ` Daniel Campbell
2017-01-18  7:48                         ` Sam Jorna
2017-01-07  2:58                     ` M. J. Everitt
2017-01-07  2:47                   ` M. J. Everitt
2017-01-04 10:34             ` Thomas Kahle
2017-01-03 14:31         ` [gentoo-dev] Packages up for grabs due to retirement M. J. Everitt
2017-01-03 14:34           ` Damien LEVAC
2017-01-04  3:11             ` Mart Raudsepp
2017-01-06  4:33               ` Kent Fredric
2017-01-06  6:00           ` Daniel Campbell [this message]
2017-01-06  8:04             ` Mart Raudsepp
2017-01-03 11:14       ` Lars Wendler
  -- strict thread matches above, loose matches on Subject: below --
2018-03-03  7:38 Johann Schmitz (ercpe)
2018-03-03  8:40 ` Geaaru

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=7a2010ad-185c-514a-c11f-7000b09e4ff5@gentoo.org \
    --to=zlg@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