bike/gbootroot
1
0
Fork 0
mirror of https://github.com/fspc/gbootroot.git synced 2025-02-23 09:03:23 -05:00
Code Issues Projects Releases Wiki Activity

Update on explanation of versioning replacements.

Browse Source
This commit is contained in:
freesource 2001-12-07 02:40:59 +00:00
parent 7ef6926d9c
commit effc568b3e
1 changed files with 19 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
doc/html/index.html
View File

@ -3,7 +3,7 @@
<body text="#000000" bgcolor="#FFFFFF" link="#0000EF" vlink="#51188E" <body text="#000000" bgcolor="#FFFFFF" link="#0000EF" vlink="#51188E"
alink="#FF0000"> alink="#FF0000">
<center>$Id: index.html,v 1.38 2001/12/06 22:01:20 freesource Exp $</center> <center>$Id: index.html,v 1.39 2001/12/06 23:14:40 freesource Exp $</center>
<p> <p>
@ -606,21 +606,34 @@ Replacements
from add-ons are placed in the from add-ons are placed in the
/usr/share/gbootroot/yard/Replacements directory.&nbsp;&nbsp; /usr/share/gbootroot/yard/Replacements directory.&nbsp;&nbsp;
When a user opens up gBootRoot, the program checks to see if there are any 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 $HOME/.gbootroot/yard/Replacements directory to the
replacements repository.&nbsp;&nbsp; replacements repository.&nbsp;&nbsp;
In general the repository for replacements is owned by root, so normal 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 users can't make changes to these files; however, when root is
it a policy always to make changes from the $HOME location while using editing replacements in the $HOME Replacements location, it should be the
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 administrator will not be able to
make any changes to the replacements repository because the CVS directories make any changes to the replacements repository because the CVS directories
keep date information which prevents the editing of these keep date information which prevents the editing of these
files.&nbsp;&nbsp;It is highly recommended to follow this procedure, and files.&nbsp;&nbsp;It is highly recommended to follow this procedure, and
not to delete the CVS directories because /usr/share is meant to be used 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 <a href="http://www.pathname.com/fhs/">FHS</a>).</p> (see <a href="http://www.pathname.com/fhs/">FHS</a>).</p>
<p>
<em>Note for users of version 1.2.14 or earlier</em>: 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.&nbsp;&nbsp;
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.
<p>
<a name="5"><b>Can I use a program linked to uClibc in the template?</b></a>&nbsp;&nbsp;<a href="#FAQ">[back]</a></p> <a name="5"><b>Can I use a program linked to uClibc in the template?</b></a>&nbsp;&nbsp;<a href="#FAQ">[back]</a></p>
<p> <p>