scsh-conservatory
/
scsh-install-lib
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

*** empty log message ***

This commit is contained in:
michel-schinz 2004-05-22 10:45:30 +00:00
parent 8e199e877b
commit dc8bd5b49b
3 changed files with 47 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
NEWS Normal file
View File

@ -0,0 +1,17 @@
Changes in version 1.1 (released 2004-05-22)
--------------------------------------------
The installation library itself is now installed as a scsh package
called "install-lib". The "scsh-install-pkg" script is just a wrapper
around this library.
As a consequence, the meaning of the "--prefix" option passed to the
installation script changed: it is now the prefix to use to install
the "install-lib" package. All the files but the wrapper script are
installed below this prefix, according to the chosen layout. The
wrapper script itself is put in the directory specified by the
"--bindir" option.
To comply with the packaging policy, some files were also renamed.
Most importantly, the name of the documentation changed from
"proposal.pdf" to "install-lib.pdf".

4
get-version.scm Executable file
View File

@ -0,0 +1,4 @@
#!/bin/sh
scsh -l scheme/install-lib/install-lib-version.scm -c \
'(display (string-join (map number->string install-lib-version) "."))'

26
scheme/install-lib/install-lib-version.scm Normal file
View File

@ -0,0 +1,26 @@
;;
;; Version of the installation library
;;
;; The versioning scheme is as follows: a version is composed of three
;; integers called (from left to right) "major", "minor" and
;; "revision".
;;
;; Two versions which share a "major" and "minor" number must be fully
;; compatible in that one should be exchangeable for the other without
;; (important) change in behaviour.
;;
;; Two versions which share a "major" number must be compatible in an
;; ascendent fashion: the features offered by the version with the
;; greatest "minor" number must be a superset of those offered by the
;; other.
;;
;; Two versions which do not even share a "major" number can be
;; mutually incompatible.
;;
;; Clients using the installation library must specify which "major"
;; and "minor" number they need --- if the above scheme is respected,
;; the "revision" should not matter. This need is satisfied if the
;; requested "major" number matches the one of the library, and the
;; requested "minor" is smaller or equal to the one of the library.
(define install-lib-version '(1 1 0))