This is the mail archive of the
guile@sourceware.cygnus.com
mailing list for the Guile project.
Sharing Guile source
- To: guile at sourceware dot cygnus dot com
- Subject: Sharing Guile source
- From: Mikael Djurfeldt <mdj at mdj dot nada dot kth dot se>
- Date: Sat, 20 May 2000 18:43:21 +0200
- Cc: gang-of-four at red-bean dot com
- Reply-to: Mikael Djurfeldt <djurfeldt at nada dot kth dot se>
The module system needs to and will take time.
I think we could set up some way of sharing Guile source already now.
I think we should make a draft of a standard for Guile modules.
Issues which needs to be standardized are:
1. Hierarchical name space.
Modules will almost certainly have names like (ice-9 from outer space).
We should standardize some of this name space:
(math ...) for math
(oop ...) for OO programming
etc.
I think Maciej and Jim have worked on this.
Do you have any material?
2. Structure of a module package.
A module could be distributed as a standard GNU tar archive with the
customary `configure' script. We could make a template module (such a
thing already exists, guile-template) or a tool which can generate the
framework of a module.
3. Some way of uploading and distributing modules.
We could, for example, use ftp or CVS.
Is there a way to make uploading of packages easy also for new people?
A write-only ftp directory with maintainers manually moving the
contribution to the right place is the traditional way.
Is it possible to automatically give a new user write-access to his
own contribution, and to let him place it at the correct place without
intervention from the maintainers? To prevent misuse the maintainers
would keep an eye on the archive and remove "bad" modules. To get
basic security the system would ensure that the author has a real
email account in the same way as modern list management programs.