[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNU-traductores] gnudist:/home/www/html/server/standards/README.html --
gnudist's file diff daemon
[GNU-traductores] gnudist:/home/www/html/server/standards/README.html -- recent changes
Wed, 15 Aug 2001 06:16:58 -0700 (PDT)
This is an automated report from gnudist.
Recent changes to /home/www/html/server/standards/README.html:
19 -rw-rw-r-- 1 webcvs www 17703 Aug 14 08:05
--- /tmp/diffmon25679 Wed Aug 15 06:16:58 2001
+++ /home/www/html/server/standards/README.html Tue Aug 14 08:05:22 2001
@@ -162,21 +162,72 @@
Since CVS is not able to handle symbolic links, a simple mechanism has
been implemented on the machine hosting the www.gnu.org to allow
webmasters to control the symbolic link from the CVS tree.
+By adding special files (".symlinks") into the CVS tree that are
+interpreted as specficiations to build symbolic links. The
+"symlinks" script can be run immediately after a "cvs update"
+to fix the symbolic links according to the specifications
+included in the ".symlinks" files.
+The current directory is searched recursively for ".symlinks" files.
+Symbolic links that exist in directory where there is no
+.symlinks files will be ignored. Only directories containing a
+.symlinks file are handled.
+Each symbolic link specification from the ".symlinks" file is honored,
+i.e. the symbolic link is created if it does not exist yet. If a
+symbolic link is found in the directory and is not listed in the
+".symlinks" file, it is removed.
+Special handling to comply to the GNU webmaster standard
+is also applied. If a subdirectory "foo/bar" has no
+"foo/bar/index.html" file and a file "foo/bar/bar.html"
+exists, then a symbolic link from "index.html" to
+"bar.html" is created even if it is not listed in the
+.symlinks file. In short, an implicit
+ cd foo/bar ; ln -s bar.html index.html
+Symbolic links that point outside the web site
+document root are ignored.
-The special file <b>.symlinks</b> contains a list of file name pairs,
-one per line. For instance:
+The ".symlinks" files obey to the following format.
+Each line starting with a sharp sign ("#") is treated as a
+comment and ignored.
+Lines that do not contain two strings separated by white
+space are silently ignored.
+Here is an example of .symlinks file content:
+ # Link foo.html to bar.html.
+ # Stricly equivalent to ln -s foo.html bar.html
+ foo.html bar.html
+On each line the first file name must be a relative path
+name to an existing file. The file designated by this path
+must not be outside the document root. The second file
+name may not contain any slash, it is the name of the sym-
+bolic link to be created.
-is a valid <b>.symlinks</b> file. Every night a script reads all the
-<b>.symlinks</b> files, prepend a <i>ln -s</i> in front of each line
-and execute them. Well, in reality it's not that simple but you get
-the idea. The <b>.symlinks</b> file can only be used to control the
-symbolic links in the directory where they are. File names with "/" in
-them will be ignored. For example, "../../gpl/gpl.html".
+The actual command used to implement this feature is symlinks(1) and
+the sources can be found in
<H4><A NAME="SEC1" HREF="README.html#TOC1">Style guidelines</A></H4>
@@ -406,7 +457,7 @@
permitted in any medium, provided this notice is preserved.<P>
<!-- timestamp start -->
-$Date: 2001/07/03 06:29:10 $ $Author: rms46 $
+$Date: 2001/08/14 15:05:11 $ $Author: loic $
<!-- timestamp end -->
- [GNU-traductores] gnudist:/home/www/html/server/standards/README.html -- recent changes,
gnudist's file diff daemon <=