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

[Clément Pit-Claudel]

On 18/05/2020 16.17, Yoni Rabkin wrote:
> Once it is on ELPA, would that make the MELPA version redundant? Are
> packages duplicated across ELPA and MELPA? If so, why?

Some are duplicated, others not.  I expect any user who has MELPA to have ELPA 
as well, so duplication isn't necessary to reach everyone.
One difference is that by default, MELPA builds a package for every push to the 
master branch of your git repository, while ELPA requires an update to the 
version field of the package header.

> Once Emms is available on ELPA, people who want Emacs' package manager
> to install it will have it available. At that point it would be very
> strange, and confusing, to have an identical copy of Emms separately
> maintained via MELPA.

It wouldn't matter much, I think; but since MELPA uses commit date as its 
version numbers, people who use both repos would by default get the newer 
builds from your git repository.

> 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.

Well, publishing to MELPA doesn't really require any maintenance, as evidenced 
by 8 years and 50k downloads ^^

> Thank you for all of your patience as I'm learning this.

Thanks for your dedication and for developing emms.