[Savannah-cvs] administration/docs/hacking_savannah hacking_sa...

[Sylvain Beucler]

CVSROOT:        /cvsroot/administration
Module name:    administration
Branch:         
Changes by:     Sylvain Beucler <address@hidden>        04/08/22 16:13:41

Modified files:
        docs/hacking_savannah: hacking_savannah.texi 

Log message:
        Various fixes

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/administration/administration/docs/hacking_savannah/hacking_savannah.texi.diff?tr1=1.34&tr2=1.35&r1=text&r2=text

Patches:
Index: administration/docs/hacking_savannah/hacking_savannah.texi
diff -u administration/docs/hacking_savannah/hacking_savannah.texi:1.34 
administration/docs/hacking_savannah/hacking_savannah.texi:1.35
--- administration/docs/hacking_savannah/hacking_savannah.texi:1.34     Sun Aug 
22 11:39:24 2004
+++ administration/docs/hacking_savannah/hacking_savannah.texi  Sun Aug 22 
16:13:41 2004
@@ -1,5 +1,5 @@
 \input texinfo   @c -*-texinfo-*-
address@hidden $Id: hacking_savannah.texi,v 1.34 2004/08/22 11:39:24 Beuc Exp $
address@hidden $Id: hacking_savannah.texi,v 1.35 2004/08/22 16:13:41 Beuc Exp $
 @comment %**start of header
 @setfilename hacking_savannah.info
 @include version.texi
@@ -260,14 +260,14 @@
 It is still incomplete.
 
 Basically, it describes how I made [am making] a Savannah test install
-on my faithful PI-133
+on my faithful PI-133.
 
 The PI-133 reference, besides doing homage to my computer from fall
 1996, shows that you can use any old machine to make your test
 installation.
 
 This chapter provides as much information as possible on the way
-Savannah currently is. It does not document the way it @emph{should
+Savannah currently is; it does not document the way it @emph{should
 be}, so feel free to make suggestions.
 
 
@@ -337,7 +337,9 @@
 @section WWW root directory
 
 All services related to the WWW will be run into a different root
-directory (@pxref{chroot invocation, , , , coreutils}).
+directory (@pxref{chroot invocation, chroot, @command{chroot}: Run a
+command with a different root directory, coreutils, @sc{GNU}
+Core-utils}).
 
 Let's create the new root:
 @example
@@ -448,6 +450,7 @@
 @example
 $ cd /usr/src
 $ cvs -d:pserver:anonymous@@cvs.gna.org:/cvs/savane co savane
+$ cd savane
 $ ./configure # say no to interactive configuration
 $ make
 $ make database
@@ -473,7 +476,7 @@
 at least explain it]
 
 @example
-$ cd etc
+$ cd /savanah/etc
 $ ln -s savane/gnu-conf
 $ ln -s savane/nongnu-conf
 @end example
@@ -484,6 +487,7 @@
 Last, make the default configuration path point to the WWW root:
 @example
 $ cd /etc
+$ rm -rf savannah
 $ ln -s /savannah/etc/savane/gnu-conf savannah
 @end example
 
@@ -519,6 +523,9 @@
 At this point, you should be able to see Savane's default homepage
 when pointing your browser at your test machine.
 
+Now, you need to tune the Savannah configuration files to your installation.
+our $sys_default_domain="dott";
+
 
 @node Remaining,  , Savane, Savannah configuration
 @section Remaining
@@ -650,20 +657,20 @@
 
 To actually create the list, run the following commands from the shell:
 
address@hidden/var/mailman/bin/newlist}
address@hidden/var/mailman/bin/newlist}
 When prompted enter the list name, the list owner email address and
 an initial pasword.  (Use common sense when choosing the password; 
 make sure it's >= 6 characters long and used at least letters and
 numbers.)
 
address@hidden /var/mailman/lists/<new-list-name>/domains}
address@hidden /var/mailman/lists/<new-list-name>/domains}
 Create the `domains' directory.
 
address@hidden /var/mailman/lists/<new-list-name>/domains/gnu.org}
address@hidden /var/mailman/lists/<new-list-name>/domains/gnu.org}
 If the the list you are creating is for a GNU project, touch the
 file `gnu.org' in the list's `domains' subdirectory.
 
address@hidden /var/mailman/lists/<new-list-name>/domains/nongnu.org}
address@hidden /var/mailman/lists/<new-list-name>/domains/nongnu.org}
 Otherwise, for non-GNU projects, touch the file `nongnu.org' in the
 list's `domains' subdirectory.