unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: Sharlatan Hellseher <sharlatanus@gmail.com>,
	guix-devel <guix-devel@gnu.org>
Subject: Re: Question on the process of packge withdrawal
Date: Tue, 28 Feb 2023 11:30:21 +0100	[thread overview]
Message-ID: <87r0uajd4y.fsf@gmail.com> (raw)
In-Reply-To: <CAO+9K5pgp=ZKBTjtU=hYNZExYWC0TQP9GLEqwNXRQ_tJ3KY0Tg@mail.gmail.com>

Hi,

On dim., 26 févr. 2023 at 20:11, Sharlatan Hellseher <sharlatanus@gmail.com> wrote:

>   Other example
>   <https://git.savannah.gnu.org/cgit/guix.git/commit/?id=ba17b160ed7d09ef58183c22b6f1b10ee7ba926d>
>   the reason it's not updated at <http://www.catb.org/~esr/> -
>   development was moved to <https://gitlab.com/esr/reposurgeon>.

I proposed to remove the package because it was broken and no one was
willing to fix it.  What is the point to keep broken packages?

Here, the timeline:

Report broken:    4 Dec 2018 (4 years, 12 weeks, 1 day ago)
Try update:      13 Jul 2022 (32 weeks, 5 days, 20 hours ago)
Propose removal: 17 Oct 2022 (19 weeks, 14 hours, 57 seconds ago)
Send patch:      21 Jan 2023 (5 weeks, 2 days, 18 hours ago)
Commit patch:    21 Jan 2023

Well, the two “improvements“ here could be, IMHO:

 a) send patch to guix-patches instead of the bug report itself,
 b) wait some days between send and commit.


>   That tendency concerns me as a packager it's not clear for me which
>   criterias were used to make a division to withdraw the package(s). The
>   age of project is not always a good measure for example example,
>   [Common Lisp] ecosystem has quite ancient packages (5-8y old of not
>   touched since the last commit) but still in active use (check
>   [pgloader])

From my point of view, the first rule is if the package still builds or
not.  If the package is broken, let try to fix and if it is not possible
because unmaintained or else, then let drop it.

The second rule is if the package is a leaf or not.  More dependants the
package has and more effort should be put in fixing it, IMHO.

The third rule is about security.  From my point of view, old packages
with known vulnerabilities are not appealing for working on fixing it.

Else, if the package still builds, I do not see why it would be removed.
Old unmaintained (or barely maintained) packages* are very common in
scientific context and they just still works very well. :-)

*as linear algebra libraries wrote long time ago using good ol’
 Fortran. ;-)  Still the state of art.


Cheers,
simon


  parent reply	other threads:[~2023-02-28 10:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-26 20:11 Question on the process of packge withdrawal Sharlatan Hellseher
2023-02-27 17:12 ` Maxim Cournoyer
2023-02-27 19:55   ` Leo Famulari
2023-02-28 10:30 ` Simon Tournier [this message]
2023-02-28 16:26   ` bokr
2023-02-28 17:16     ` Simon Tournier
2023-03-01  9:40       ` Bengt Richter
2023-02-28 14:57 ` Andreas Enge
2023-02-28 17:10   ` Leo Famulari

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r0uajd4y.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=sharlatanus@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).