[e-cvs] cvs commit: e/src/esrc/scripts setup.e

[markm@eros.cs.jhu.edu]

markm       01/12/23 15:04:02

  Modified:    src/csrc/setup README.txt
               src/esrc/scripts setup.e
  Log:
  The 0.8.10 release.  Some installation doco improvements.

Revision  Changes    Path
1.7       +30 -11    e/src/csrc/setup/README.txt

Index: README.txt
===================================================================
RCS file: /cvs/e/src/csrc/setup/README.txt,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- README.txt	2001/04/05 01:21:59	1.6
+++ README.txt	2001/12/23 20:04:02	1.7
@@ -135,13 +135,22 @@
 "${{<property name>}}" according to the comments in the respective new
 files.
 
-If you have no need for a bash driver script for your system, you
-needn't bother creating "e".  If this is useful for you, place "e"
-somewhere on your PATH, such as "~/bin/e" for a personal install, or
-such as "/usr/local/bin/e" for a system install.  E scripts assume you
-have "/usr/bin/env" installed on your system, as they begin with
-"#!/usr/bin/env e".
+E scripts by convention begin with "#!/usr/bin/env e".  So if you wish
+to run E scripts directly as executables, you will need to have
+"/usr/bin/env" installed on your system.  This looks on your PATH for
+its argument, so you will need to install the "e" driver script (made
+in the previous step) on your path.  This is a bash script, and
+requires a bash >= 2.01 to be installed as "/bin/bash".  To check your
+bash version, type
 
+    $ echo $BASH_VERSION
+
+For Mac OS X, a bash 2.05 (as of this writing) is available at 
+http://www.apple.com/downloads/macosx/unix_apps_utilities/bashthegnubourneagainshell.html
+
+If you can't find an adequate bash for your system, you can still run
+E scripts the old fashioned way, as explained below under Running E.
+
 When doing a manual install, don't worry about "winfo.txt", it isn't
 relevant.  (It's only for helping the automatic installer, and to
 supplement bug reports.)
@@ -163,8 +172,8 @@
 E scripts by double clicking on them.  The right button menu should
 give you more choices as well.
 
-If you have bash installed on your system you can use it to run
-scripts simply by:
+If you have /bin/bash >= 2.01 installed on your system you can use it
+to run scripts simply by:
 
     % e <script>.e <args...>
 
@@ -172,7 +181,9 @@
 
     #!/usr/bin/env e
 
-and is executable (as E scripts should be), then you can simply say
+and is executable (as E scripts should be), and you have
+"/usr/bin/env" installed on your system (as all *nix systems seem to
+these days), then you can simply say
 
     % <script>.e <args...>
 
@@ -183,9 +194,17 @@
 
     % e --help
 
-Please report bugs to bugs@erights.org
-
 
                    Reporting Bugs
 
 
+Please report bugs to bugs@erights.org or enter them in our bug
+tracking system at 
+"https://bugs.sieve.net/bugs/?func=addbug&group_id=16380".
+
+Please include any diagnostic out that appears.
+
+If the installation attempt produced a winfo.txt file (in the
+installation directory), then please include it as well.
+
+Thanks.



1.22      +5 -1      e/src/esrc/scripts/setup.e

Index: setup.e
===================================================================
RCS file: /cvs/e/src/esrc/scripts/setup.e,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- setup.e	2001/12/12 06:35:57	1.21
+++ setup.e	2001/12/23 20:04:02	1.22
@@ -89,6 +89,10 @@
 
 } else {
     # XXX This is stupid.  We should do common install logic regardless.
-    println("Unrecognized OS, probably Ctrl-C to exit")
+    println("Unrecognized OS, probably Ctrl-C to exit.")
+    def readme := ehomeDir["README.txt"]
+    if (readme exists()) {
+        println(`Then read the manual install instructions in "${readme getPath()}".`)
+    }
     interp blockAtTop()
 }