MELPA?

[Chobbes]

This looks like a fantastic project!

It would be super helpful if it was available on MELPA, if somebody knows how to do that :).

[cicerojones]

👍 Truly--this is great. Thanks for your awesome work!

MELPA would help with the managing of dependencies for request and anaphora packages. I eventually figured out the import of the error messages (eval-buffer: Cannot open load file: No such file or directory, request), but others may be left scratching their respective heads.

Presumably, one problem is the existence of a package already on MELPA with the same name (I imagine that the author of that package would agree that there's much functionality in this one that supersedes his own, but that's neither here nor there).

I don't know how this is typically resolved, but, as a MELPA contributor/maintainer states here , it would be best if the authors "joined forces." What that looks like in practice, of course...?

In any event, Here's the link to the relevant section of the MELPA README on Github, which states:

Adding packages is as simple as submitting a new recipe as a pull request

i.e.

fork the project's source tree and create a pull request with a recipe for your package.

From what I can tell, all the package-creator would need to do, aside from approving the pushing up to MELPA (and of course resolving any naming issues) would be to add a file with the line:

(beeminder.el :repo "mbork/beeminder.el" :fetcher github)

But someone who has actually done this before should probably confirm and contribute to this conversation!

[mbork]

Thanks a lot!
I don't have too much time now, but I think the best course of action would be to add support for stuff present in the other package and then contact the author to switch our packages. This way, I wouldn't break anyone's setup.
I'll look into it in the following weeks.