Re: "Write a new package" culture instead of patches?

[Dmitry Gutov]

On 18.05.2020 23:13, Yoni Rabkin wrote:
> If there is some technical issue that would stop MELPA users from
> getting it from ELPA, then perhaps we could organize a way for the ELPA
> maintained copy be mirrored to MELPA. That seems like a kludge, but we
> should try to do it if that is the only way not to break people's
> installation.

MELPA requires very little maintenance.

As a package maintainer, MELPA occasionally comes handy when I fix some 
tricky bug or other, but hesitate to tag a new release version yet, and 
the user is not technical enough to check out a commit or apply a patch.

Provided the fix is in the master branch already, I can ask them to wait 
for MELPA to update (which happens within 6-12 hours) and try out the 
new snapshot version (all MELPA versions are snapshot versions).

If you really don't want this happening, yes, you might as well ask them 
to delist your package.