The information recorded and reported in the distributed system only includes the git repository (when the source is git). It would be nice if quicklisp recorded the commit hash of the code it fetched and distributes.
Eg. for hunchentoot, currently we have a label "latest-github-release" but this is meaningless. It would be more useful to have "fe7605a818409d756b72e50975c67d1497048b50".
For other git repositories, having the url of the git repository (and the commit hash) would also be more useful.
eg. for cl-base64, "kmr-git" "cl-base64" are rather useless.
It would be more useful to have something like: "9d5a88ecfd67b28c1c2b3b3497f2237e37032691" "http://git.kpe.io/cl-base64.git"
The information recorded and reported in the distributed system only includes the git repository (when the source is git). It would be nice if quicklisp recorded the commit hash of the code it fetched and distributes.
Eg. for hunchentoot, currently we have a label "latest-github-release" but this is meaningless. It would be more useful to have "fe7605a818409d756b72e50975c67d1497048b50".
For other git repositories, having the url of the git repository (and the commit hash) would also be more useful. eg. for cl-base64, "kmr-git" "cl-base64" are rather useless. It would be more useful to have something like: "9d5a88ecfd67b28c1c2b3b3497f2237e37032691" "http://git.kpe.io/cl-base64.git"
If a specific branch or tag is fetched, this could also be added with the commit hash.
( with
quick-where-from
from https://github.com/informatimago/lisp/blob/master/tools/quicklisp.lisp )