Re: What to do about unmaintained ELPA packages

[Akib Azmain Turja <akib@disroot.org>]

[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> Yeah, we can fix GNU ELPA packages, since those are part of Emacs.
>> But what about NonGNU ELPA packages?
>
> Actually, for the majority of packages, there is virtually no difference
> between GNU and NonGNU in this respect: their official development takes
> place elsewhere but we have our own branch in elpa.git/nongnu.git where
> we can install any changes we may want.
>
> And in both cases, installing changes on our own branch means that the
> development has diverged ("forked"), which will spell pain in the future
> if/when upstream's development continues.
>
> IOW: we can do it, but there are strong motivations to refrain from
> doing it.
>
>
>         Stefan
>

Then we can, as I suggested in a previous message, add UNMAINTAINED to
the summary line of the package.  Thus users will know that its no
longer maintained.  And as soon as we get an update, we can remove it.

-- 
Akib Azmain Turja

This message is signed by me with my GnuPG key.  It's fingerprint is:

    7001 8CE5 819F 17A3 BBA6  66AF E74F 0EFA 922A E7F5

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]