From: Damien LEVAC <damien.levac@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: Why lastrite when it works? (Was: Re: [gentoo-dev] Packages up for grabs due to retirement)
Date: Tue, 3 Jan 2017 09:24:19 -0500 [thread overview]
Message-ID: <589f3521-af7e-488d-8bba-4465c3a78e8e@gmail.com> (raw)
In-Reply-To: <3374938.6WoLSc5MN8@mal>
On 01/03/2017 09:14 AM, Michael Mol wrote:
> On Tuesday, January 3, 2017 12:05:10 PM EST 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.
> Do we have detailed treatise documenting the points and counterpoints to "Why
> lastrite it when it works?" It's a question that comes up every month or two,
> and the reasons, for and against, are probably mature enough to get numbers,
> now.
>
> Reason #3 in favor: "It works for me" may only be valid from a particular
> perspective. Without active maintenance, there may be subtle bugs that aren't
> immediately obvious. Bugs that aren't immediately obvious aren't always
> innocuous; sometimes they're insidious background data loss. Other times, they
> might be security vulnerabilities no good guy has yet noticed.
...and sometimes a package just stop being "actively" maintained because
it is feature-complete (as far as the goals of the project were
concerned) and just works.
The minimum conditions to lastrite something should be not actively
maintained _and_ with open bugs that either compromise security or
affect normal usage subject to the condition that it is not still used
by users. I do not think at this point in time Gentoo devs have any mean
to know the popularity of different packages, but that would be a must
to take proper decision as far as retiring packages goes.
-- Just a random Gentoo user.
next prev parent reply other threads:[~2017-01-03 14:24 UTC|newest]
Thread overview: 43+ 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 [this message]
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
2017-01-06 8:04 ` Mart Raudsepp
2017-01-03 11:14 ` Lars Wendler
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=589f3521-af7e-488d-8bba-4465c3a78e8e@gmail.com \
--to=damien.levac@gmail.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