From effc568b3e0f1f9e48f99cc8235325fe2bbacfce Mon Sep 17 00:00:00 2001 From: freesource Date: Fri, 7 Dec 2001 02:40:59 +0000 Subject: [PATCH] Update on explanation of versioning replacements. --- doc/html/index.html | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-) diff --git a/doc/html/index.html b/doc/html/index.html index e767128..012bdfb 100644 --- a/doc/html/index.html +++ b/doc/html/index.html @@ -3,7 +3,7 @@ -
$Id: index.html,v 1.38 2001/12/06 22:01:20 freesource Exp $
+
$Id: index.html,v 1.39 2001/12/06 23:14:40 freesource Exp $

@@ -606,21 +606,34 @@ Replacements from add-ons are placed in the /usr/share/gbootroot/yard/Replacements directory.   When a user opens up gBootRoot, the program checks to see if there are any -new replacements and then creates symlink from the +new replacements and then creates symlinks from the $HOME/.gbootroot/yard/Replacements directory to the replacements repository.   In general the repository for replacements is owned by root, so normal -users can't make changes to these files anyways; however, root should make -it a policy always to make changes from the $HOME location while using -an editor which respects versioned files (i.e. Emacs). Then the +users can't make changes to these files; however, when root is +editing replacements in the $HOME Replacements location, it should be the +administrator's policy to use an editor which respects versioned files (i.e. Emacs). Then the administrator will not be able to make any changes to the replacements repository because the CVS directories keep date information which prevents the editing of these files.  It is highly recommended to follow this procedure, and not to delete the CVS directories because /usr/share is meant to be used -for data which shouldn't be modified +for data which shouldn't be modified directly by any user (see FHS).

+

+ +Note for users of version 1.2.14 or earlier: Verions of gbootroot +before 1.3.0 didn't have this set-up, instead there were just copies of add-on +replacements in the $HOME replacement directory to allow the user +to directly modify add-on replacements.   +In order to get the full benefit of the new change you will need to +rename any of the $HOME/.gbootroot/yard/Replacements +you've modified and put them in a safe place, then remove the old +replacements, and return the renamed replacements. + +

+ Can I use a program linked to uClibc in the template?  [back]