Hi again and thanks for commiting the diffs,
Will official releases still have the asd files at the top level like other asdf packages? If not, would it make sense to move those at the first level but to keep the code under src?
A script adding all the first level package directories to asdf:*central-registry* can no longer work with iolib >0.6.0 unless it also locates asd files or unless I "mv src/* ." for instance.
Although this isn't a major problem, I've been wondering as all other packages I've used have asd files at the first level. In case it was your intention to move the asd files only back to the package's root, here is attached a diff (tested against 20090217's tarball snapshot, and applied after "mv src/*.asd ." to avoid the diff -N mess for such minor changes).
Thanks,
On Wed, 2009-02-18 at 03:16 -0500, Matthew Mondor wrote:
Hi again and thanks for commiting the diffs,
Will official releases still have the asd files at the top level like other asdf packages?
Yes - for personal æesthetic reasons: I want the top directory do be uncluttered
A script adding all the first level package directories to asdf:*central-registry* can no longer work with iolib >0.6.0 unless it also locates asd files or unless I "mv src/* ." for instance.
I don't like very much the use of a script to automatically add directories to asdf:*central-registry* . In case of your development machine you're much better off with using a single directory + symlinks, and in case of automatic deployment I think that keeping an explicit MANIFEST file containing the path of all enabled .asd files is much better.
-
Attila Lendvai -
Matthew Mondor -
Stelian Ionescu