[Fusionforge-commits] r7836 - trunk/gforge/debian

Christian Bayle cbayle at libremir.placard.fr.eu.org
Sat Jun 13 12:49:23 CEST 2009


Author: cbayle
Date: 2009-06-13 12:49:23 +0200 (Sat, 13 Jun 2009)
New Revision: 7836

Modified:
   trunk/gforge/debian/README.Debian
Log:
Small updates, more needed


Modified: trunk/gforge/debian/README.Debian
===================================================================
--- trunk/gforge/debian/README.Debian	2009-06-13 10:14:04 UTC (rev 7835)
+++ trunk/gforge/debian/README.Debian	2009-06-13 10:49:23 UTC (rev 7836)
@@ -1,18 +1,18 @@
-GForge for Debian
+ at FORGENAME@ for Debian
 =================
 
 Status
 ------
 Want to know what the status of this package is?  Read
-/usr/share/doc/pkgname/TODO.Debian or (even better)
-<http://savannah.gnu.org/support/?group_id=259>.  If you miss a
+/usr/share/doc/@PACKAGE@/TODO.Debian or (even better)
+<https://fusionforge.org/mediawiki/index.php/Roadmap>.  If you miss a
 feature, or find a bug, or want to help, don't hesitate to contact me
 (Roland Mas <lolando at debian.org>) .  Plenty of features are missing,
 I'm working on some, but if you don't tell me which ones you miss the
 most I might process them in the wrong order for you.
 
   Please read the bug reports on the Debian bug-tracking system (at
-<URL:http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=pkgname>)
+<URL:http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=@PACKAGE@>)
 before submitting new ones.  Be warned that bug reports describing a
 problem precisely and/or offering a solution will probably be
 processed faster :-)
@@ -29,22 +29,22 @@
 
 Installation notes
 ------------------
-  GForge is a big piece of software.  It's far-reaching.  It
+  @FORGENAME@ is a big piece of software.  It's far-reaching.  It
 fiddles with many different parts of the system.  As automated as I
 have tried to make its installation, there are still things that need
 to be done by hand, maybe even by a system administrator.
 
-  First, you'll need a hostname.  Get the pkgname.<your-domain>
+  First, you'll need a hostname.  Get the @PACKAGE at .<your-domain>
 DNS name to be created, pointing on the IP address of the host you're
-installing GForge on.  The "pkgname" part isn't required, you
+installing @FORGENAME@ on.  The "@PACKAGE@" part isn't required, you
 can call it however you like.  However, I'll assume you chose
-"pkgname" from now on; substitute as needed.
+"@PACKAGE@" from now on; substitute as needed.
 
   If you want to use the Apache virtual hosting service, you'll even
 need a delegation of a subdomain.  Get your system administrator to
-delegate you the SOA for the pkgname.<your-domain> subdomain.
-This will allow GForge to create new hostnames for projects when
-needed (foo.pkgname.<your-domain>, for instance), as well as some
+delegate you the SOA for the @PACKAGE at .<your-domain> subdomain.
+This will allow @FORGENAME@ to create new hostnames for projects when
+needed (foo. at PACKAGE@.<your-domain>, for instance), as well as some
 hostnames needed by the system (for mailing-lists or SCM, for
 instance).
 
@@ -55,9 +55,9 @@
 any case, since it would make the data contained in the LDAP directory
 inconsistent with the real data stored in the PostgreSQL database.
 
-  You'll need a configured MTA for GForge.  Depending on whether
-the GForge users are local or remote, you might need to set up a
-smarthost or something else.  GForge depends on a working mail
+  You'll need a configured MTA for @FORGENAME at .  Depending on whether
+the @FORGENAME@ users are local or remote, you might need to set up a
+smarthost or something else.  @FORGENAME@ depends on a working mail
 system, and you won't be able to create user accounts without it.  I'm
 not sure yet what advanced tricks need to be done with the MTA.  There
 might be some stuff to do with virtual domains for mailing-lists or
@@ -70,13 +70,13 @@
 Otherwise, just use mod-ssl-makecert as advised during the
 configuration phase, and get your own custom certificate.
 
-  Do *not* delete the /etc/pkgname/*.template files.  They are
+  Do *not* delete the /etc/@PACKAGE@/*.template files.  They are
 needed.  Do not alter them either unless you *know* what you're doing.
 
 
 Adminning notes
 ---------------
-  Once GForge is setup, it pretty much runs by itself.  There
+  Once @FORGENAME@ is setup, it pretty much runs by itself.  There
 should be relatively few things to do for the administrator.  The
 following are random notes trying to document them.
 
@@ -88,20 +88,20 @@
   If you need to add skills to the database after installation, you
 can use the sf-add-skill script.  Give it a skill (or a list of
 skills) and it'll insert it into the databse.  This script is located
-in /usr/share/pkgname/bin/.
+in /usr/share/@PACKAGE@/bin/.
 
   For cvs to work you have to add a symlink doing
-ln -s /var/lib/pkgname/chroot/cvsroot /cvsroot.
+ln -s /var/lib/@PACKAGE@/chroot/cvsroot /cvsroot.
 We can't do this for Debian policy reason that forbid this.
   For svn similar 
-ln -s /var/lib/pkgname/chroot/svnroot /svnroot is to be done
+ln -s /var/lib/@PACKAGE@/chroot/svnroot /svnroot is to be done
 
   Don't forget about adding 
-SYSLOGD="-p /dev/log -a /var/lib/pkgname/chroot/dev/log" in /etc/default/syslog
+SYSLOGD="-p /dev/log -a /var/lib/@PACKAGE@/chroot/dev/log" in /etc/default/syslog
 This is a WARNING you might have seen at install, essential if you run 
 anonymous cvs in a root jail (This is the default in Debian)
 
-  If you would like to add a theme to your GForge, you'll first
+  If you would like to add a theme to your @FORGENAME@, you'll first
 have to compose it.  Please refer to README.Themes.
 
   Other customisations are described in README.Custom.
@@ -109,9 +109,9 @@
 
 Thanks
 ------
-  Apart from the GForge crew at VA Linux, who did (and probably
+  Apart from the SourceForge crew at VA Linux, who did (and probably
 still do) a great job with SF, I'd like to send my thanks to Guillaume
-Morin, who wrote a very thorough GForge installation guide.  That
+Morin, who wrote a very thorough SourceForge installation guide.  That
 guide gives step-by-step instructions for the installation procedure,
 and a big part of the packaging task was to turn these instructions
 into automated scripts.  Even if this package has evolved a lot since




More information about the Fusionforge-commits mailing list