4 ms·
I haven't counted the number of packages I use, from MELPA, but it's likely around 100. I have problems associated with MELPA about 2-3 times per year. One of
by Expez 12y ago
I haven't counted the number of packages I use, from MELPA, but it's likely around 100. I have problems associated with MELPA about 2-3 times per year.
One of these times was yesterday, when cider-test was added to cider. Melpa excludes files ending with -test.el by default, so a file was missing. I grabbed the file manually from github and went on with my evening. An hour or so later the pull request fixing the problem was merged.
For developers, the criticism against MELPA is just FUD. If anything goes wrong you can fix it easily enough.
- lvh 12y agoI agree that MELPA is mostly a good thing. However, even if the software there works fine, that doesn't address the criticisms of MELPA that the author talks about in his article: version numbers, rebuild times, effort and abuse to add a stable designated version. (The author of the article makes elpy, an excellent Python development environment, where occasionally, a component gets modernized. This is the case right now with the refactoring logic. MELPA gives you a broken elpy, joergen has no reasonable way to override it even for people who also subscribe to his personal package index, etc. :-))