Andreas Rottmann <[email protected]> writes: > - Systems: A system is the "unit of software" dorodango works with. It > has a name (a symbol, possibly along with a namespace tag), and a > version, which may be used to form dependency relationships among > packages. > > A system's files are grouped into categories (e.g. (R6RS) libraries, > documentation). Each category contains a set of (relative) > filenames. The actual filenames need not directly correspond to the > filenames of the bundle they are contained in; A system definition may > specify a mapping (see below). > > - sys-def.scm files: They contain the name, version, dependencies, file > mapping, etc. for one or more systems, each described by a > `define-system' form, for example: > > % cat dorodango/sys-def.scm > (define-system dorodango > (version 0) > (depends spells srfi) > (documentation "doc" ("Readme.txt" -> "README"))) > > % cat spells/sys-def.scm > (define-system spells > (version 0) > (depends srfi) > (documentation "doc") > (libraries "spells")) > I've slighly changed my mind on this: to be more in-line with R6RS's `library' form, the syntax should probably be more like:
(system (<name> . <version>) <other-stuff> ...) This also makes apparent the possibility of hierarchical names, but I'm not gonna worry about that for now. The file name is now also not fitting any more (not that I was that happy about it before), how about "systems.doro"? Regards, Rotty -- Andreas Rottmann -- <http://rotty.yi.org/>
