Go to file
mainzelm e511c905cd WRITE seems more useful for debugging output 2005-10-11 15:40:44 +00:00
scheme WRITE seems more useful for debugging output 2005-10-11 15:40:44 +00:00
.gitignore *** empty log message *** 2004-09-14 11:54:00 +00:00
AUTHORS Auxiliary files 2005-10-04 13:38:24 +00:00
COPYING Auxiliary files 2005-10-04 13:38:24 +00:00
Makefile Auxiliary files 2005-10-04 13:38:24 +00:00
NEWS Auxiliary files 2005-10-04 13:38:24 +00:00
README Auxiliary files 2005-10-04 13:38:24 +00:00
install.scm Minor fix for header output 2005-10-04 14:47:11 +00:00
pkg-def.scm Definitions for install-lib 2004-09-14 12:36:04 +00:00

README

Commander S 1.0 README					-*- outline -*-


                                                   Tuebingen, October 2005


			     Commander S
                             ===========

* Requirements

  Before installing Commander S, you need to install the following
  software:

  - The current CVS version of scsh, the Scheme Shell.  The latest
    release, version 0.6.6, contains two small bugs that prevent
    Commander S from running correctly. Alternativly, you may apply
    the patches listed in the last section of this README to your scsh
    0.6.6 source tree.
    (From <http://www.scsh.net>)

  - Version 1.2.0 of install-lib, the scsh installation library
    (From <http://lamp.epfl.ch/~schinz/scsh_packages/scsh-install-lib-1.2.0.tar.gz>)

  - Version 1.0 of scsh-ncurses, the scsh bindings for ncurses
    (From <ftp://ftp.scsh.net/pub/scsh/packages/scsh-ncurses/scsh-ncurses-1.0.tar.gz>)

  - Version 0.8 of Sunterlib, the Scheme Untergrund library (NOT
    RELEASED YET)
    (From <http://savannah.nongnu.org/download/sunterlib/sunterlib-0.8.tar.gz>)

* Installation

  Run the script install.scm from the top of the tarball:

  ./install.scm

  The only important option is --prefix to specify a directory where
  files are installed. Use the --help options to see all possible
  options.

* Patches for scsh

  The following patches fix two little bugs in the scsh source tree
  found during the development of Commander S.

Index: scsh/procobj.scm
===================================================================
RCS file: /cvsroot/scsh/scsh/scsh/procobj.scm,v
retrieving revision 1.22
diff -u -r1.22 procobj.scm
--- scsh/procobj.scm	14 Aug 2002 14:45:33 -0000	1.22
+++ scsh/procobj.scm	5 Jul 2005 15:11:50 -0000
@@ -345,8 +345,10 @@
 
 ;;; All you have to do, if a wait on proc was successful
 (define (waited-by-wait proc status)
-  (obituary proc status)
-  (mark-proc-waited! proc))
+  (if (not (status:stop-sig status))
+      (begin
+	(obituary proc status)
+	(mark-proc-waited! proc))))
 
 ;;; we know from somewhere that proc is dead
 (define (obituary proc status)

Index: scsh-interfaces.scm
===================================================================
RCS file: /cvsroot/scsh/scsh/scsh/scsh-interfaces.scm,v
retrieving revision 1.55.2.5
retrieving revision 1.55.2.6
diff -u -c -r1.55.2.5 -r1.55.2.6
*** scsh-interfaces.scm	15 Apr 2004 13:01:35 -0000	1.55.2.5
--- scsh-interfaces.scm	30 May 2005 12:59:05 -0000	1.55.2.6
***************
*** 406,411 ****
--- 406,412 ----
  
  (define-interface scsh-user/group-db-interface
    (export user-info
+           user-info?
  	  user-info:name
  	  user-info:uid
  	  user-info:gid
***************
*** 416,421 ****
--- 417,423 ----
  	  ->username
  
  	  group-info
+           group-info?
  	  group-info:name
  	  group-info:gid
  	  group-info:members