LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

Fixed various dead links, updated my personal URL and added new ACL tool information.

This commit is contained in:
vivekv 2005-11-13 05:15:03 +00:00
parent e370a93989
commit c9ff115112
1 changed files with 46 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

67
LDP/ref/docbook/CVS-BestPractices/cvs-bestpractices.xml
View File

@ -2,11 +2,11 @@
<!-- $Id$ -->
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
<!-- Document version -->
<!ENTITY DOCVERSION "0.6">
<!ENTITY DOCVERSION "0.7">
<!-- File Includes -->
<!ENTITY GFDL-FILE SYSTEM "gfdl.xml">
@ -17,7 +17,7 @@
<!ENTITY CVSAB "CVS">
<!ENTITY SCMAB "SCM">
<!ENTITY SCM "Software configuration management">
<!ENTITY MYEMAIL "vivek at magic-cauldron.com">
<!ENTITY MYEMAIL "vivekv at yahoo dot com">
<!-- All the best practices described in one place.... -->
<!ENTITY section2-useguiclient "Use GUI &CVSAB; client">
@ -30,6 +30,7 @@
<!ENTITY section2-checkin "Check-in Often">
<!ENTITY section1-serverconfig "&CVSAB; Server Configuration">
<!ENTITY section2-accesscontrol "&CVSAB; access control">
<!ENTITY section2-scripting "Server side scripting">
<!ENTITY section2-notification "Server Notification">
@ -46,7 +47,7 @@
<!ENTITY section1-softwarebuild "Software Builds">
<!ENTITY section2-bebo "Build Early and Build Often">
<!ENTITY section2-automate "Automate build Process completely">
<!ENTITY section2-ensurecheckin "All necessary files must be checked before build">
<!ENTITY section2-ensurecheckin "All necessary files must be checked-in before build">
<!ENTITY section1-instprocess "Institutionalize &CVSAB; in the Organization">
<!ENTITY section2-chngmgmt "Implement Change Management Process">
<!ENTITY section2-objectives "Make &CVSAB; Usage part of Objectives">
@ -66,6 +67,13 @@
</author>
<revhistory>
<revision>
<revnumber>0.7</revnumber>
<date>2005-10-15</date>
<authorinitials>vv</authorinitials>
<revremark>A bunch of minor fixes as suggested by readers.</revremark>
</revision>
<revision>
<revnumber>0.6</revnumber>
@ -166,14 +174,14 @@ deploying &CVSAB; in his or her organization. Some of the popular
<orderedlist>
<listitem>
<para>The <ulink url="http://www.cvshome.org">&CVS; site</ulink> where
<para>The <ulink url="http://ximbiot.com/cvs/wiki/index.php?title=Main_Page">&CVS; site</ulink> where
current informaton about CVS is available. Including the <ulink
url="http://www.cvshome.org/docs/manual/cvs.html">&CVSAB; manual</ulink>.
url="http://ximbiot.com/cvs/wiki/index.php?title=Cederqvist">&CVSAB; manual</ulink>.
</para>
</listitem>
<listitem>
<para>Karl Fogel's book <emphasis>Open Source Development with
CVS</emphasis> has GPL'd sections <ulink url="http://cvsbook.red-bean.com">available online.</ulink>
<para>Karl Fogel's book, <ulink url="http://cvsbook.red-bean.com">Open Source Development with
CVS</ulink> is available online.
</para>
</listitem>
@ -218,7 +226,7 @@ document, and would like to be notified of any plans to redistribute the same.
the concepts, examples and other content at your own risk. As this is a new
edition of this document, there may be errors and inaccuracies that may of
course be damaging to your system. Proceed with caution, and although this is
highly unlikely, the author(s) do not take any responsibility for that.
highly unlikely, the author(s) do not take any responsibility whatsoever.
</para>
<para> All copyrights are held by their respective owners, unless specifically
@ -236,19 +244,19 @@ major installation and backups at regular intervals. </para> </sect2>
<sect2 id="newversions">
<title>New Versions</title>
<para> The version number of this document is &DOCVERSION;. </para>
<para> This document is Version : &DOCVERSION;. </para>
<para> The latest version of this document can be obtained from </para>
<para> The latest version of this document can be obtained from (In the order of latest version availability) </para>
<orderedlist>
<listitem>
<para>
<ulink url="http://www.magic-cauldron.com/cm/cvs-bestpractices/index-cvs-bestpractices.html">My website</ulink>
<ulink url="http://www.sanchivi.com/cm/cvs-bestpractices/index-cvs-bestpractices.html">My website</ulink>
</para>
</listitem>
<listitem>
<para>
<ulink url="http://www.tldp.org/doc.html#cvs_bestpractices">The linux documentation project</ulink>
<ulink url="http://tldp.org/REF/CVS-BestPractices/html/index.html">The linux documentation project</ulink>
</para>
</listitem>
</orderedlist>
@ -339,6 +347,10 @@ additions, comments and criticisms to the following email address :
<para><xref linkend="section1-serverconfig"/>
</para>
<itemizedlist>
<listitem>
<para><xref linkend="section2-accesscontrol"/>
</para>
</listitem>
<listitem>
<para><xref linkend="section2-scripting"/>
</para>
@ -538,13 +550,11 @@ name will ensure that the sandboxes are kept up to date. </para>
<sect2 id="section2-workinside" xreflabel="&section2-workinside;" >
<title>&section2-workinside;</title>
<para>The sandbox can be thought of as a controlled area within which
&CVSAB; can track for changes made to the various source files. Files
belonging to other developers will be automatically updated by &CVSAB;.
Thus the developer who lives within the sandbox will stand to gain a lot of
benefits of concurrent development. This benefit cannot be achieved for
work done outside a sandbox. </para>
<para>The sandbox can be thought of as a controlled area within which &CVSAB;
can track for changes made to the various source files. Files belonging to
other developers will be automatically updated by &CVSAB; in the developer's
sandbox. Thus the developer who lives within the sandbox will stand to gain
a lot of benefits of concurrent development. </para>
</sect2>
@ -593,6 +603,21 @@ them. Thus, audit trail can be established if necessary. </para>
configuration.
</para>
<sect2 id="section2-accesscontrol" xreflabel="&section2-accesscontrol;">
<title>&section2-accesscontrol;</title>
<para>One of the important questions that I have been asked time and again is the
ability to have access control for files/folders/branches etc., within
the &CVSAB; repository for various users. Unfortunately &CVSAB; does not
come with a built in Access control capability but it does support a
rudimentary form of access control through the readers/writers files in
the CVSROOT repository. I have put together a set of scripts that use
the readers/writers files to provide a slightly useable version of access
control. This is available at <ulink
url="http://cvspermissions.sarovar.org">http://cvspermissions.sarovar.org</ulink>
as an &OPENSOURCE; project. Feel free to use it and let me know how it
works for you. </para>
</sect2>
<sect2 id="section2-scripting" xreflabel="&section2-scripting;">
<title>&section2-scripting;</title>