Anthony Carrico <firstname.lastname@example.org> writes:
> I have finally got back to the packages proposal. I'm trying the cvs
> version. It looks good. I'll keep playing with it.
I'm glad to hear that, thanks.
> (define-package <name> <version> <extensions> <body> ...) (syntax)
> What are <extensions> used for? The documentation doesn't say.
Yes, I still have to document that. For now you can look at the
following message which should make it clear:
> What if I want to initialize <version> from an expression? Do I use a
> function version of define-package? So maybe <version> should be
> quasiquote too.
Ok, I will quasiquote it too. Just out of curiosity, what use do you
want to make of that? Do you want to read the version from a file, or
something like that?
> FEATURE REQUEST:
> Compute an installation file's contents from an expression. So this:
> (install-string <string> <file> <location> [<target-dir>] [<perms>])
> would write the <string> to the <file>.
Sounds reasonable and useful, I'll add that ASAP (which should mean
this week-end). Maybe instead of a string we could pass an
s-expression, like for write-to-load-script.
> 1. Unrecognized layout ("hfs" instead of "fhs" below), gives exception
> instead of error message.
I'll fix that, thanks for finding it.
> 2. relative prefix doesn't work.
Right, but I think I'll disallow relative prefixes (with a better
error message than the current one), like "configure" does. I don't
think they are really useful, but can be misleading especially when
used along with --dest-dir.