unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jimmy Aguilar Mena <jimmy.aguilar@bsc.es>
To: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA] Package cleanup
Date: Wed, 30 Mar 2022 06:56:02 +0200	[thread overview]
Message-ID: <20220330045602.4j55nyt52lyib3c6@Ergus> (raw)
In-Reply-To: <E1nZOkg-0000nY-G1@fencepost.gnu.org>

On Tue, Mar 29, 2022 at 11:12:06PM -0400, Richard Stallman wrote:
>[[[ To any NSA and FBI agents reading my email: please consider    ]]]
>[[[ whether defending the US Constitution against all enemies,     ]]]
>[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
>Thanks for investigating the situation with unmaintained packages.
>What you've found will help us think about what to do.
>
>  > Just a question. Did you finally agreed about the package
>  > obsoletion/removal procedure for ELPA?
>
>I'd like to see a proposal.
>
I have seen some discussions about this topic before. See bellow.

>  > It seems there are some packages there which haven't received any update
>  > in a very long time (>5 years).
>
>That suggests they might have bugs and need maintenance,
>but it does not imply they are useless or obsolete.
>They might be obsolete, or not.
>
>There are many questions we'd want to check
>to decide what to do with each package.
>
But if they don't receive any update for years, and the bug reports
accumulate (on github too) then it quite possible that either the users
and the maintainers are not interested on it anymore.

>  > I have found some packages that doesn't even work or rely on some
>  > features that were obsoleted or removed.
>
>In those cases, we clearly don't want to leave the package there
>in its current form.  But what change should we make?
>
>We could delete it.  We could look for people to update it.
>Either one might be better, depending on more details.
>
We could archive it in a different repository in case someone desires to
adopt, check or fork in the future. Or we could also flag it somehow to
say to the package-list that it is orphan, obsolete,
unmaintained... That's the approach in the AUR repository for arch Linux
and it is useful; because the users get a warning during the updates
about abandon, orphan or outdated packages.

Then if a package is in that state for too long it may be archived, so
it can be accessed, but is not offered in the package list as a good
alternative.
>
>-- 
>Dr Richard Stallman (https://stallman.org)
>Chief GNUisance of the GNU Project (https://gnu.org)
>Founder, Free Software Foundation (https://fsf.org)
>Internet Hall-of-Famer (https://internethalloffame.org)
>
>



  parent reply	other threads:[~2022-03-30  4:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-29  0:43 [ELPA] Package cleanup Jimmy Aguilar Mena
2022-03-29 16:24 ` [External] : " Drew Adams
2022-03-29 21:41   ` John Yates
2022-03-29 22:04     ` Drew Adams
2022-03-29 23:05       ` John Yates
2022-03-30  1:43         ` Drew Adams
2022-03-31  4:27         ` Richard Stallman
2022-03-30  7:31       ` Michael Albinus
2022-03-30  8:35     ` [External] : " Stefan Monnier
2022-03-30 14:09       ` Jimmy Aguilar Mena
2022-03-30 21:23         ` Stefan Monnier
2022-03-31  4:27     ` Richard Stallman
2022-03-30  3:12 ` Richard Stallman
2022-03-30  3:44   ` Po Lu
2022-03-30  7:56     ` João Távora
2022-03-30  4:56   ` Jimmy Aguilar Mena [this message]
2022-04-01  4:07     ` Richard Stallman

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://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=20220330045602.4j55nyt52lyib3c6@Ergus \
    --to=jimmy.aguilar@bsc.es \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.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).