Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upAdd support for Emacs packages #212
Comments
|
Wanted to check in on this. The main problem here is that MELPA does not have an API that we can hit to get the correct repo to redirect to. See melpa/melpa#2850. There is a bit of a workaround by hitting in archives.json but the file is pretty large (Nearly a full Megabyte) which may be a little much to handle with live-resolver. Im curious how @stefanbuck and @josephfrazier feel about this approach, and if they think it would be feasible to do this with live-resolver. |
|
Thanks for following up on this. I think we could start off by simply having the live-resolver hit archive.json on every request. Then, if performance/bandwidth is an issue, or if we want to be nicer to melpa.org, we could add in caching based on the I'll see if I can get this working on the live-resolver. If you've started work on this repo, feel free to open a PR, even if it's just work-in-progress so far. |
|
I actually started my work by looking at how to get the live-resolver to work with MELPA. Ill start work on this with the assumption that we will get live-resolver working with archive.json. |
As discussed with @benjamreynolds in OctoLinker/OctoLinker#212, this makes it possible to use `/q/melpa/{package}` to get the URL from https://melpa.org/archive.json.
… header This reduces response time and bandwidth use, as mentioned in OctoLinker/OctoLinker#212 (comment)
|
Oops, sorry for the duplicate work! I put together a MELPA resolver at OctoLinker/api#41, if you want to take a look. |
* Add MELPA resolver As discussed with @benjamreynolds in OctoLinker/OctoLinker#212, this makes it possible to use `/q/melpa/{package}` to get the URL from https://melpa.org/archive.json. * melpa-resolver: Cache https://melpa.org/archive.json by Last-Modified header This reduces response time and bandwidth use, as mentioned in OctoLinker/OctoLinker#212 (comment) * melpa-resolver: Don't hardcode lastModified date Even though it works, it looks magical and could be confusing. See #41 (comment)
|
AWESOME! now that the live-resolver for Melpa is up, Ill take a crack at the browser extension work when I get some time this week. It shouldnt be too difficult. |
|
Yup, I decided to go ahead and merge OctoLinker/api#41 to make it easier for to you work on this, without having to run a local instance of live-resolver. I look forward to seeing how it goes! As I mentioned earlier, feel free to open a PR as soon as you'd like, even if it doesn't work yet. |
This should be relatives straightforward. Most emacs dependencies are declared in a
Caskfile,require'd directly in a file with a.elextension or declared withuse-packageThis should be pretty straightforward and similar in implementation to when
vimrcsupport was added. .I think I should be able to handle it if no one opposes me taking a crack at it.