Releases and Quicklisp
Closed this issue · 9 comments
Quicklisp used to get parse-number-1.3.tar.gz from github, but github doesn't offer that kind of service any more. Is it possible to set up a permanent link to something like parse-number-latest.tar.gz for Quicklisp to use? Should I start using git master instead?
You can use the new release URLs: https://github.com/sharplispers/parse-number/archive/v1.3.tar.gz
Is it possible to set up a parse-number-latest.tar.gz like slime does?
One way to do it would be to maintain a "latest-release" branch. It's not great, but it'd work.
@quicklisp, I've made an explicit release now. Is it good enough ? It seems to be what @luismbo does for Slime
What is the URL for the release tar.gz?
I thought the link "Latest" on the release page pointed to the tarball, but it doesn't. I won't create & upload tarballs manually any more so I suggest you use he Github JSON API to deal with releases: https://developer.github.com/v3/repos/releases/
@sionescu My suggestion was to use a "latest-release" tag (or branch, whichever) so that you get a .../latest-release.tar.gz URL. With SLIME, a release scripts updates a tarball at c-l.net...
The Release API is not particularly convenient. You have to grab the list of releases, decide which one is the latest (perhaps by filtering out draft releases and sorting the rest by the "published_at" date), then retrieve the appropriate tarball.
It may not be very convenient, but it can be reused for all Github projects. Anyway, I won't create tarballs any more.