cvs commit: BLFS/edguide/chapter04 checkfiles.xml commit.xml introduction.xml updatechangelog.xml updatecredits.xml updateindex.xml

markh at linuxfromscratch.org markh at linuxfromscratch.org
Sun Jul 7 15:08:02 PDT 2002


markh       02/07/07 15:08:02

  Modified:    edguide/chapter04 checkfiles.xml commit.xml introduction.xml
                        updatechangelog.xml updatecredits.xml
                        updateindex.xml
  Log:
  update edguide to fit new book layout
  
  Revision  Changes    Path
  1.2       +5 -4      BLFS/edguide/chapter04/checkfiles.xml
  
  Index: checkfiles.xml
  ===================================================================
  RCS file: /home/cvsroot/BLFS/edguide/chapter04/checkfiles.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- checkfiles.xml	29 May 2002 15:47:21 -0000	1.1
  +++ checkfiles.xml	7 Jul 2002 22:08:02 -0000	1.2
  @@ -4,17 +4,16 @@
   
   <para>If you are adding files, you need to have ran a <userinput>cvs
   add</userinput> command on each of them (something like <userinput>cvs
  -add packages/m/mypackage*.xml</userinput> often does the trick.  A good
  +add mypackage*.xml</userinput> often does the trick.  A good
   trick if you've only added files (not taken any away) is to run a
   <userinput>cvs up</userinput> which will give an output something like
   this:
   <screen>mark:~/LFS/BLFS$ cvs up
   ? temp/thisfileneedstobeadded
   cvs server: Updating .
  -cvs server: Updating appendixa
  +cvs server: Updating appendices
   [snip]
  -cvs server: Updating packages/z
  -cvs server: Updating parts
  +cvs server: Updating postlfs  
   cvs server: Updating preface
   cvs server: Updating temp
   A temp/thisfileadded
  @@ -37,6 +36,8 @@
   cvs server: Updating template</screen>
   [snip]'s added by me!  If you look at the first column, you will see
   various different letters which all mean different things.</para>
  +
  +
   
   <para><userinput>?</userinput>: This is what CVS reports when it doesn't
   know what to do with a file.  Generally it means that you've forgotten
  
  
  
  1.2       +2 -2      BLFS/edguide/chapter04/commit.xml
  
  Index: commit.xml
  ===================================================================
  RCS file: /home/cvsroot/BLFS/edguide/chapter04/commit.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- commit.xml	29 May 2002 15:47:21 -0000	1.1
  +++ commit.xml	7 Jul 2002 22:08:02 -0000	1.2
  @@ -22,8 +22,8 @@
   <userinput>cvs ci</userinput> command.  A good example of a commit
   command could be:
   <screen><userinput>cvs ci -m "add new package baldrick" index.xml \
  -chapter01/changelog.xml chapter01/credits.xml \
  -chapter17/chapter17.xml packages/b/baldrick*.xml</userinput></screen>
  +introduction/welcome/changelog.xml introduction/welcome/credits.xml \
  +postlfs/postlfs.xml postlfs/config/baldrick/baldrick*.xml</userinput></screen>
   If you have only made the changes regarding this package to your tree,
   then you can save time by simply running:
   <screen><userinput>cvs ci -m "add new package
  
  
  
  1.2       +3 -3      BLFS/edguide/chapter04/introduction.xml
  
  Index: introduction.xml
  ===================================================================
  RCS file: /home/cvsroot/BLFS/edguide/chapter04/introduction.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- introduction.xml	29 May 2002 15:47:21 -0000	1.1
  +++ introduction.xml	7 Jul 2002 22:08:02 -0000	1.2
  @@ -8,11 +8,11 @@
   <itemizedlist>
   <listitem><para>Test the instructions you are adding</para></listitem>
   <listitem><para>Update <filename>index.xml</filename> with the new date
  -and / or updated entities if necessary.</para></listitem>
  +and the files containing updated entities if necessary.</para></listitem>
   <listitem><para>Update
  -<filename>chapter01/changelog.xml</filename></para></listitem>
  +<filename>introduction/welcome/changelog.xml</filename></para></listitem>
   <listitem><para>Update
  -<filename>chapter01/credits.xml</filename></para></listitem>
  +<filename>introduction/welcome/credits.xml</filename></para></listitem>
   <listitem><para>Check that all relevant files have been <userinput>cvs
   add</userinput>'d or <userinput>remove</userinput>'d.</para></listitem>
   <listitem><para>Check that the book renders properly.</para></listitem>
  
  
  
  1.3       +1 -1      BLFS/edguide/chapter04/updatechangelog.xml
  
  Index: updatechangelog.xml
  ===================================================================
  RCS file: /home/cvsroot/BLFS/edguide/chapter04/updatechangelog.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- updatechangelog.xml	8 Jun 2002 01:09:14 -0000	1.2
  +++ updatechangelog.xml	7 Jul 2002 22:08:02 -0000	1.3
  @@ -1,5 +1,5 @@
   <sect1 id="ch04-updatechangelog">
  -<title>Update chapter01/changelog.xml</title>
  +<title>Update introduction/welcome/changelog.xml</title>
   <?dbhtml filename="updatechangelog.html" dir="chapter04"?>
   
   <para>Changelog updates should <emphasis>always</emphasis> be provided
  
  
  
  1.2       +1 -1      BLFS/edguide/chapter04/updatecredits.xml
  
  Index: updatecredits.xml
  ===================================================================
  RCS file: /home/cvsroot/BLFS/edguide/chapter04/updatecredits.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- updatecredits.xml	29 May 2002 15:47:21 -0000	1.1
  +++ updatecredits.xml	7 Jul 2002 22:08:02 -0000	1.2
  @@ -1,5 +1,5 @@
   <sect1 id="ch04-updatecredits">
  -<title>Update chapter01/credits.xml</title>
  +<title>Update introduction/welcome/credits.xml</title>
   <?dbhtml filename="updatecredits.html" dir="chapter04"?>
   
   <para>This file contains the list of who wrote what.  We should try and
  
  
  
  1.2       +5 -7      BLFS/edguide/chapter04/updateindex.xml
  
  Index: updateindex.xml
  ===================================================================
  RCS file: /home/cvsroot/BLFS/edguide/chapter04/updateindex.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- updateindex.xml	29 May 2002 15:47:21 -0000	1.1
  +++ updateindex.xml	7 Jul 2002 22:08:02 -0000	1.2
  @@ -11,12 +11,10 @@
   the format YYYYMMDD.</para></sect2>
   
   <sect2><title>Adding / updating entities</title>
  -<para>Entities should be on one line (even if this requires wrapping
  -because of the length).  Package entities should always be added in
  -alphabetical order; if needed, create the <-- X --> divider (where
  -X == any letter!).  Most letters probably have their dividers by now but some
  -still don't.  We may soon divide <filename>index.xml</filename> into
  -entity files (as of the time of writing, it's a tad under 30Kb which is
  -too big for my liking).</para></sect2>
  +<para>Package entities are now stored in individual
  +<filename>.ent</filename> files throughout the BLFS CVS tree.  You need
  +to find the relevant ones and update them.  Entities should be on one line 
  +(even if this requires wrapping because of the length).</para>
  +</sect2>
   
   </sect1>
  
  
  
-- 
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe blfs-book' in the subject header of the message



More information about the blfs-book mailing list