summaryrefslogtreecommitdiff
path: root/module/scripts
diff options
context:
space:
mode:
authorNeil Jerram <neil@ossau.uklinux.net>2011-03-21 09:05:59 +0000
committerNeil Jerram <neil@ossau.uklinux.net>2011-03-25 19:45:14 +0000
commitc6e05396dc73c3bcfa71b92b4689e8cb6d4588eb (patch)
treede6b0d31d1319af1e0a8b3ff1c19c0154186b50f /module/scripts
parent6b8bc6f8b507928f9b0bd71000f5132c984db798 (diff)
downloadguile-c6e05396dc73c3bcfa71b92b4689e8cb6d4588eb.tar.gz
Remove statements about scripts/* that are no longer true
* doc/ref/tools.texi (Executable Modules): Say "guile-tools modules" instead of "executable modules". Remove obsolete statements about not ending in .scm, being executable, and beginning with shell script invocation sequence. * module/scripts/README: Ditto.
Diffstat (limited to 'module/scripts')
-rw-r--r--module/scripts/README23
1 files changed, 5 insertions, 18 deletions
diff --git a/module/scripts/README b/module/scripts/README
index 56dd286fb..cb397f5d2 100644
--- a/module/scripts/README
+++ b/module/scripts/README
@@ -4,9 +4,9 @@ Overview and Usage
This directory contains Scheme programs, some useful in maintaining Guile.
On "make install", these programs are copied to PKGDATADIR/VERSION/scripts.
-You can invoke a program from the shell, or alternatively, load its file
-as a Guile Scheme module, and use its exported procedure(s) from Scheme code.
-Typically for any PROGRAM:
+You can use guile-tools to invoke a program from the shell, or alternatively,
+load its file as a Guile Scheme module, and use its exported procedure(s)
+from Scheme code. Typically for any PROGRAM:
(use-modules (scripts PROGRAM))
(PROGRAM ARG1 ARG2 ...)
@@ -22,8 +22,6 @@ To see PROGRAM's commentary, which may or may not be helpful:
(help (scripts PROGRAM))
-To see all commentaries and module dependencies, try: "make overview".
-
If you want to try the programs before installing Guile, you will probably
need to set environment variable GUILE_LOAD_PATH to be the parent directory.
This can be done in Bourne-compatible shells like so:
@@ -40,11 +38,7 @@ How to Contribute
See template file PROGRAM for a quick start.
-Programs must follow the "executable module" convention, documented here:
-
-- The file name must not end in ".scm".
-
-- The file must be executable (chmod +x).
+Programs must follow the "guile-tools" convention, documented here:
- The module name must be "(scripts PROGRAM)". A procedure named PROGRAM w/
signature "(PROGRAM . args)" must be exported. Basically, use some variant
@@ -61,15 +55,8 @@ Programs must follow the "executable module" convention, documented here:
However, `main' must NOT be exported.
-- The beginning of the file must use the following invocation sequence:
-
- #!/bin/sh
- main='(module-ref (resolve-module '\''(scripts PROGRAM)) '\'main')'
- exec ${GUILE-guile} -l $0 -c "(apply $main (cdr (command-line)))" "$@"
- !#
-
Following these conventions allows the program file to be used as module
-(scripts PROGRAM) in addition to as a standalone executable. Please also
+(scripts PROGRAM) in addition to being invoked by guile-tools. Please also
include a helpful Commentary section w/ some usage info.