⚓ Permalink

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16

;; foo.asd</p>

<p>(asdf:defsystem :foo
  :version #.(with-open-file (f (merge-pathnames "version.lisp-expr"</p>

<pre><code>                                             (or *compile-file-pathname*
                                                 *load-truename*)))
           (read f))
</code></pre>

<p>...)</p>

<p>;; and version.lisp-expr</p>

<p>;; -<em>- lisp -</em>-
"0.0.1"

Q: Why this approach ?
A: Because it's script-friendly: I have a generic release script that overwrites version.lisp-expr before committing and tagging, and it's much safer to do it this way rather than using sed to replace the version string in .asd files. Also because this way the version info says in one place, instead of duplicating it in multiple files.

Q: Why use cl:read ?
A: Because it allows me to add comments to the file. Since I use #. to include the version, the format must be a CL string.

Q: Why .lisp-expr instead of .lisp ?
A: To make it obvious that the file isn't meant to be compiled, but that the syntax is CL. It's technically unnecessary.

Q: Where did I get this idea from ?
A: SBCL. Its build system includes version.lisp-expr only in release tarballs and computes the version using git-describe in source checkouts, but for most needs that's unnecessarily complex.

⚓ Permalink

If you can't wait until the next Quicklisp update, download them and let me know if you encounter any issues

⚓ Permalink

I created a new project for it on common-lisp.net with its own mailing list, converted the sources to git and put them on github.

I'll slowly integrate the various forks and patches I found around so if you have feature requests or you're just interested join fiveam-devel.

⚓ Permalink