On Jun 19, 2009, at 9:43 PM, leppie wrote:
The simplest way is to just wrap up all the source files in a
archive[1] file and provide a named manifest in the root of the
archive.
The manifest will contain information such as the library name,
version, etc.
This is pretty much how debian packages work.
[1] Not sure about what can be used here.
Anything would work I guess. Zip files are probably good enough.
The implementation is then to provide the rest of the
implementation details.
Sure.
PS: what to do about centralized distribution and updates?
I don't mind hosting the packages (for all R6RS implementations, not
just Ikarus). I also don't mind hosting only a list of pointers to
the locations of the packages, possibly with periodic caching.
To start, who is volunteering for writing the specs for the package
manifest files? (about 2 pages, starting with: A package manifest
file is called MANIFEST which contains an S-expression that's an
association list, ...)
Aziz,,,
