On Fri, Feb 06, 2004 at 11:28:08AM +0100, Michel Schinz wrote:
> 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?
Yes, or even just to set the version number from a variable.
For example, I have a lot of experimenting to do before I settle on a
packaging scheme for Sunterlib, but one option would be to create
packages for each constituent library. In this case, the Sunterlib
version number could be used as the version for each package, and of
course I wouldn't want to have to update the version number in every
package definition. In reality, I would probably give each package its
own version number. That would be nicer, since it would preserve the
data about which packages change between sunterlib versions.
> > 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.
In this case, the file I want to write would contain text, not sexps.
I could imagine wanting to write other stuff some day, like xml or
something, who knows? The point is that you don't always want to keep
every file in source control, or even in the distribution package. You
can keep your distribution smaller by auto-generating such things at
install time.
--
Anthony Carrico
signature.asc
Description: Digital signature
|