This is the mail archive of the guile@cygnus.com mailing list for the guile project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
>>>>> "Jim" == Jim Blandy <jimb@red-bean.com> writes:
Jim> @item
Jim> At install time, a module should be able to check that any other modules
Jim> it needs are already installed, and warn the user of any missing
Jim> prerequisites.
In addition, a standard module versioning method should be available
which will allow one module to require that another module be "at
least version 'N.M' or later" and/or "no later than version N+n.M+m",
and to declare its own version for use by the same require mechanism.
(I.e., imagine the following sequence, which I've experienced with
Emacs Lisp, Perl, Tcl and others:
1. Package A is released as "Version 1.0"
2. Package A is re-released as "Version 2.0"
3. Package B, based on "A V2.0", is released as "Version 1.0"
4. Hapless user finds two different FTP sites, downloads
"A V1.0" and "B V1.0", then sends out email asking why B doesn't work.
I've also experienced the reverse, when an upgrade to A breaks B. I
expect we'll see this when ctax or whatever is released for Guile 2.0
but most of the world is using 1.3 ...)
--
Lee Thomas lee_thomas@credence.com (503)-520-6551
Senior Software Quality Engineer
Credence Systems Corporation, Beaverton, OR, USA