Hallo folks,
I'm currently working an a installation-script for SCX, which contains
C-Code and an optional support for the Xft library. I changed the
script of Michel, so that the user can activate the optional part on
the command-line, and that the pkg-def has access to the dry-run?
variable, to make the C configuration and compilation 'dry', too.
I appended the script to this mail...
The optional parts can be specified in an additional field in the
package-definition, which is an associtation list, that could be used
for more things. One specifies a name, a description (which shows up
in the usage) and a default state (active or not):
(define-package name version ((optional-parts (id "Description of id" #f)))
body)
An additional option for every optional-part is added to the script like this:
--with-id=[yes|no] Description of id [no]
and in the package-defition body one can call
(with-optional-part? 'id)
and the access to the dry-run? variable is done through
(is-running-dry?)
Comments welcome...
If you (and the others :-) like it Michel, you can put it on your
homepage of course...
--
David Frese
txthJOoQWNV4w.txt
Description: Text document
txtaX9JGzhsO4.txt
Description: Text document
|