From 2ac06ddb0e708e9adb2886d0184aadc8ca3f998b Mon Sep 17 00:00:00 2001 From: freesource Date: Tue, 11 Dec 2001 05:39:57 +0000 Subject: [PATCH] This adds info about the other arch-depend replacements repository. --- doc/html/index.html | 23 ++++++++++++++--------- 1 file changed, 14 insertions(+), 9 deletions(-) diff --git a/doc/html/index.html b/doc/html/index.html index c256db6..60e5141 100644 --- a/doc/html/index.html +++ b/doc/html/index.html @@ -3,7 +3,7 @@ -
$Id: index.html,v 1.42 2001/12/08 07:10:32 freesource Exp $
+
$Id: index.html,v 1.43 2001/12/08 23:05:20 freesource Exp $

@@ -612,22 +612,27 @@ This allows developers who create add-ons (ex: make-debian-x11) to remain confident that any changes made to add-on replacements will remain available to all users.   Replacements -from add-ons are placed in the -/usr/share/gbootroot/yard/Replacements directory.   +from add-ons are placed in the archictecture-independent +/usr/share/gbootroot/yard/Replacements directory, and the +archictecture-dependent /usr/lib/bootroot/yard/Replacements +directory.   When a user opens up gBootRoot, the program checks to see if there are any 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 +replacement repositories.   +In general the repositories for replacements are owned by root, so normal 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'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 directly by any user +files.  The files kept in /usr/lib are usually binary files +specific to the host architecture, +where as the files linked from /usr/share are often text files compatible +with any architecture; however, +this directory is meant to be used for data which shouldn't be modified +directly by any user (see FHS).