gwking at metabang.com
Mon Sep 7 17:02:44 UTC 2009
On Sep 6, 2009, at 11:13 PM, Robert Goldman wrote:
> Should I expect the *ASDF-REVISION* variable to work for me? Right
> it's NIL. Is the definition of *ASDF-REVISION* a holdover from the
> days, and no longer working, or is this YA case where there's
> about git that I'm missing? Should I be doing something with the git
> pull that will get me a tags directory?
*asdf-revision* both works and doesn't work. The mechanism I found to
fill in git related metavariables was `git archive`. This only files
stuff in on the tarball and the linked version of asdf.lisp. The
variables in the git repo that you get by cloning/pulling don't have
the magic variables converted and so so *asdf-revision* isn't much
help. In practice, this means that people who get ASDF via git
directly don't get the revision number whereas people who get ASDF via
the tarball or the source file do.
If there is a better way, I'm all eyes.
(this sounds rather gross, but maybe a post pull hook could grab that
latest tag out of the repo and munge that into the source... ?)
Gary Warren King, metabang.com
Cell: (413) 559 8738
Fax: (206) 338-4052
gwkkwg on Skype * garethsan on AIM * gwking on twitter
More information about the asdf-devel