r1566 - in nALFS/hackers_guide/trunk: . introduction/welcome part2 part2/common part2/hacker

jwrober at linuxfromscratch.org jwrober at linuxfromscratch.org
Thu Oct 14 19:52:16 PDT 2004


Author: jwrober
Date: 2004-10-14 20:52:14 -0600 (Thu, 14 Oct 2004)
New Revision: 1566

Added:
   nALFS/hackers_guide/trunk/part2/common/svn.xml
   nALFS/hackers_guide/trunk/part2/hacker/svn.xml
Removed:
   nALFS/hackers_guide/trunk/part2/common/cvs.xml
Modified:
   nALFS/hackers_guide/trunk/index.xml
   nALFS/hackers_guide/trunk/introduction/welcome/changelog.xml
   nALFS/hackers_guide/trunk/part2/common/common.xml
   nALFS/hackers_guide/trunk/part2/hacker/hacker.xml
   nALFS/hackers_guide/trunk/part2/part2.ent
Log:
cvs to svn conversion

Modified: nALFS/hackers_guide/trunk/index.xml
===================================================================
--- nALFS/hackers_guide/trunk/index.xml	2004-10-13 03:02:20 UTC (rev 1565)
+++ nALFS/hackers_guide/trunk/index.xml	2004-10-15 02:52:14 UTC (rev 1566)
@@ -8,8 +8,8 @@
         Revision:          $LastChangedRevision$ 
 -->
 
-<!ENTITY version "1.2-0.2">
-<!ENTITY releasedate "October 12th, 2004">
+<!ENTITY version "1.2-0.3">
+<!ENTITY releasedate "October 14th, 2004">
 
 <!ENTITY % book         SYSTEM "book/book.ent">
 <!ENTITY % preface      SYSTEM "preface/preface.ent">

Modified: nALFS/hackers_guide/trunk/introduction/welcome/changelog.xml
===================================================================
--- nALFS/hackers_guide/trunk/introduction/welcome/changelog.xml	2004-10-13 03:02:20 UTC (rev 1565)
+++ nALFS/hackers_guide/trunk/introduction/welcome/changelog.xml	2004-10-15 02:52:14 UTC (rev 1566)
@@ -12,6 +12,11 @@
 
 <itemizedlist>
 
+<listitem><para>October 14th, 2004 [jwrober]: Finsihed off the update to
+SVN from CVS.  Added a new page to the core code hackers area and moved
+the verbiage from the common SVN page to there.  This will set up for
+specific SVN stuff for profiles and docs.</para></listitem>
+
 <listitem><para>October 12th, 2004 [jwrober]: Updated multiple pages to
 replect the change to SVN.  Also updated the distro_tarballs page to
 provide clearer instructions.</para></listitem>

Modified: nALFS/hackers_guide/trunk/part2/common/common.xml
===================================================================
--- nALFS/hackers_guide/trunk/part2/common/common.xml	2004-10-13 03:02:20 UTC (rev 1565)
+++ nALFS/hackers_guide/trunk/part2/common/common.xml	2004-10-15 02:52:14 UTC (rev 1566)
@@ -15,7 +15,7 @@
 
 </sect1>
 
-&common-cvs;
+&common-svn;
 &common-bugzilla;
 
 </chapter>

Deleted: nALFS/hackers_guide/trunk/part2/common/cvs.xml
===================================================================
--- nALFS/hackers_guide/trunk/part2/common/cvs.xml	2004-10-13 03:02:20 UTC (rev 1565)
+++ nALFS/hackers_guide/trunk/part2/common/cvs.xml	2004-10-15 02:52:14 UTC (rev 1566)
@@ -1,152 +0,0 @@
-<!--
-        Last Changed Date: $LastChangedDate$
-        Last Changed By:   $LastChangedBy$
-        Revision:          $LastChangedRevision$ 
--->
-
-<sect1 id="common-cvs" xreflabel="CVS">
-<?dbhtml filename="cvs.html" dir="common"?>
-<title>CVS</title>
-
-<sect2>
-<title>Check Out</title>
-
-<para>Bleading edge development of &book-product; occurs on HEAD in the LFS
-CVS repository. You can do an anonymous HEAD checkout by issuing the
-following command :</para>
-
-<screen><command>cvs -z9 -d :pserver:anonymous at cvs.linuxfromscratch.org:/home/cvsroot checkout ALFS/nALFS</command></screen>
-
-<para>The current stable version of &book-product; is developed on the 1.2
-branch (branch-1_2) in the LFS CVS repository. You can do an anonymous
-checkout of this branch by issuing the following command :</para>
-
-<screen><command>cvs -z9 -d :pserver:anonymous at cvs.linuxfromscratch.org:/home/cvsroot checkout -r branch-1_2 ALFS/nALFS</command></screen>
-
-</sect2>
-
-<sect2>
-<title>Usage</title>
-
-<para>The CVS repository copy of &book-product; does not include an
-executable <filename>configure</filename> script nor a
-<filename>Makefile</filename>. This is by design, as there is a script to
-create them, which ensures that their contents will always be up to date
-with the source tree contents and not require manual editing.</para>
-
-<para>&book-product; has been configured to use the GNU
-<filename>autotools</filename> suite for its build process. The build
-system was created using <filename>autoconf-2.57</filename>,
-<filename>automake-1.7.7</filename> and <filename>libtool-1.5</filename>.
-If you use older versions than those, you may experience warnings and/or
-outright failures (<filename>automake-1.6</filename> is known to be unable
-to handle the &book-product; <filename>Makefile.am</filename>) file.</para>
-
-<para>After you checkout the &book-product; source tree, you will need to
-execute:</para>
-
-<screen><command>sh ./bootstrap</command></screen>
-
-<para>in the &book-product; root directory itself. This should result
-output similar to the following:</para>
-
-<screen><command>$ sh ./bootstrap</command>
-You should update your 'aclocal.m4' by running aclocal.
-Putting files in AC_CONFIG_AUX_DIR, `gnubuild'.
-configure.ac: installing 'gnubuild/install-sh'
-configure.ac: installing 'gnubuild/mkinstalldirs'
-configure.ac: installing 'gnubuild/missing'
-Makefile.am: installing 'gnubuild/compile'
-Makefile.am: installing 'gnubuild/depcomp'
-patching file ltmain.sh
-Hunk #1 succeeded at 160 with fuzz 2 (offset -78 lines).
-Hunk #2 succeeded at 269 with fuzz 1.
-Hunk #3 succeeded at 4483 (offset -1172 lines).</screen>
-
-<para>This output comes from the <filename>autoreconf</filename> tool,
-which is part of the <filename>autoconf</filename> package, that
-automatically runs <filename>libtoolize</filename>,
-<filename>autoheader</filename>, <filename>aclocal</filename> and other
-parts of the <filename>autotools</filename> suite. The warning about
-"update your 'aclocal.m4'" can be ignored, as
-<filename>aclocal</filename> is already executed later by
-<filename>autoreconf</filename>. The <filename>patch</filename> offset
-and/or fuzz messages about <filename>ltmain.sh</filename> are caused by the
-<filename>bootstrap</filename> script applying a patch created against
-<filename>libtool-1.5</filename>; if your <filename>libtool</filename>
-version is different, the patch should still work correctly, but you may
-see messages like this from the <filename>patch</filename> command. In the
-worst case, the patch fails to apply, the &book-product; build will still
-be functional, but <filename>libtool</filename> will generate more output
-messages than necessary.</para>
-
-<para>Once <filename>bootstrap</filename> has been run, you can execute
-<filename>./configure</filename> like any other GNU autoconf-based package
-to configure &book-product; for your system.</para>
-
-</sect2>
-
-<sect2>
-<title>Editing source files</title>
-
-<para>The &book-product; build system, because it uses
-<filename>automake</filename>, has full dependency tracking on all files
-used to build the binaries. This will reduce your rebuilding time as you
-edit header files and source files, as the make system will know exactly
-what must be rebuilt.</para>
-
-<para>In addition, if you are going to make changes to
-<filename>bootstrap</filename>, you should add the
-<filename>"--enable-maintainer-mode"</filename> parameter to your
-<filename>configure</filename> command. With this done, each time you edit
-and re-run <filename>bootstrap</filename>, the
-<filename>Makefile</filename> will automatically re-run
-<filename>configure</filename> to make your changes take effect. Be warned
-though, that if you manually edit <filename>Makefile.am</filename> or
-<filename>configure.ac</filename>, you must modify the
-<filename>bootstrap</filename> script to incorporate your changes, because
-these files are not stored in the CVS repository.</para>
-
-<para>If you add any C source files to the tree, you will need to rerun the
-<filename>bootstrap</filename> script to get them included in your build.
-If you add header files, it is not necessary to rerun the
-<filename>bootstrap</filename> script unless you plan on using "make
-dist" from that same tree, in which case those added headers would not
-get included into the tarball.</para>
-
-<para>If you add or remove "syntax versions" in any of the
-handlers, you must re-run <filename>bootstrap</filename> to get the version
-lists in <filename>Makefile.am</filename> and
-<filename>configure.ac</filename> to incorporate your changes, or you will
-experience unusual build behavior.</para>
-
-<para>If you add or remove any program options in
-<filename>src/options.h</filename>, you must re-run
-<filename>bootstrap</filename> to regenerate
-<filename>src/option-list.h</filename>.  Without that file being
-regenerated, you may experience compile errors or find that your newly
-added option does not work properly.</para>
-
-<para>All other types of files fall into two categories:</para>
-
-<blockquote><para>those that should be present 
-<emphasis role="bold">only</emphasis> in the CVS repository</para>
-</blockquote>
-
-<para>Nothing needs to be done for these files, other than the relevant
-"cvs add" commands.</para>
-
-<blockquote><para>those that should be added to the distribution
-tarball</para></blockquote>
-
-<para>The <filename>bootstrap.Makefile</filename> script will need to be
-edited, specifically the line that sets <filename>EXTRA_DIST</filename>
-near the beginning of the script. Add the path(s) to the new files to this
-line, or add an additional line starting with "<filename>EXTRA_DIST
-+=</filename>" (standard GNU makefile syntax). If the files are not
-listed on this line, they will not be included in the tarball created by
-<command>make dist</command>.</para>
-
-</sect2>
-
-</sect1>

Copied: nALFS/hackers_guide/trunk/part2/common/svn.xml (from rev 1563, nALFS/hackers_guide/trunk/part2/common/cvs.xml)
===================================================================
--- nALFS/hackers_guide/trunk/part2/common/cvs.xml	2004-10-13 02:56:01 UTC (rev 1563)
+++ nALFS/hackers_guide/trunk/part2/common/svn.xml	2004-10-15 02:52:14 UTC (rev 1566)
@@ -0,0 +1,76 @@
+<!--
+        Last Changed Date: $LastChangedDate$
+        Last Changed By:   $LastChangedBy$
+        Revision:          $LastChangedRevision$ 
+-->
+
+<sect1 id="common-svn" xreflabel="SVN">
+<?dbhtml filename="svn.html" dir="common"?>
+<title>SVN</title>
+
+<sect2>
+<title>Check Out</title>
+
+<para>Bleading edge development of &book-product; occurs on the TRUNK of
+the LFS subversion (SVN) repository.</para>
+
+<para>To get a good feel for what all the repository contains, you can
+go to the SVN web at <ulink
+url="http://svn.linuxfromscratch.org/viewcvs.cgi/?root=ALFS">http://svn.linuxfromscratch.org/viewcvs.cgi/?root=ALFS</ulink></para>
+
+<para>You can do an anonymous TRUNK checkout of the &book-product;
+source code by issuing the following command :</para>
+
+<screen><command>svn co \
+svn://svn.linuxfromscratch.org/ALFS/nALFS/nALFS/trunk \
+ALFS/nALFS</command></screen>
+
+<note><para>SVN commands are very simple and similar to the Concurrent
+Version System (CVS).  When issuing an SVN "co" or
+"update" command, you should be in the top level of your local
+working "sandbox".  The above command will place the trunk of
+the &book-product; source code into the <filename>ALFS/nALFS</filename>
+directory below the root of your local working "sandbox"
+directory.  This path is arbitrary, you do not have to use
+<filename>ALFS/nALFS</filename>.</para></note>
+
+<para>If you are planning on being able to check files back in, you need
+to ensure that you do a priviledged checkout.  To do a priviledged
+checkout, add a "+ssh" just after the second "svn"
+in the above command.  Here is an example :</para>
+
+<screen><command>svn co \ 
+svn+ssh://svn.linuxfromscratch.org/ALFS/nALFS/nALFS/trunk \
+ALFS/nALFS</command></screen>
+
+<para>The books are in different places in the repository than the
+&book-product; source code.  You can find them in the following
+locations :</para>
+
+<itemizedlist>
+
+<listitem><para><emphasis role="bold">&book-product; Hackers
+Guide</emphasis> : 
+<filename>/ALFS/nALFS/docs/hackers_guide/trunk</filename></para></listitem>
+
+<listitem><para><emphasis role="bold">&book-product; Users
+Guide</emphasis> :
+<filename>/ALFS/nALFS/docs/users_guide/trunk</filename></para></listitem>
+
+<listitem><para><emphasis role="bold">ALFS Syntax
+Document</emphasis> :
+<filename>/ALFS/docs/syntax_doc/trunk</filename></para></listitem>
+
+</itemizedlist>
+
+<para>The current stable version of the &book-product; source code is
+developed on the 1.2 branch in the repository.  You can do an anonymous
+checkout of this branch by issuing the following command :</para>
+
+<screen><command>svn co \
+svn://svn.linuxfromscratch.org/ALFS/nALFS/nALFS/branches/1.2 \
+ALFS/nALFS-1.2</command></screen>
+
+</sect2>
+
+</sect1>

Modified: nALFS/hackers_guide/trunk/part2/hacker/hacker.xml
===================================================================
--- nALFS/hackers_guide/trunk/part2/hacker/hacker.xml	2004-10-13 03:02:20 UTC (rev 1565)
+++ nALFS/hackers_guide/trunk/part2/hacker/hacker.xml	2004-10-15 02:52:14 UTC (rev 1566)
@@ -18,6 +18,7 @@
 &hacker-prereqs;
 &hacker-coding-style;
 &hacker-distro-tarballs;
+&hacker-svn;
 
 </chapter>
 

Added: nALFS/hackers_guide/trunk/part2/hacker/svn.xml
===================================================================
--- nALFS/hackers_guide/trunk/part2/hacker/svn.xml	2004-10-13 03:02:20 UTC (rev 1565)
+++ nALFS/hackers_guide/trunk/part2/hacker/svn.xml	2004-10-15 02:52:14 UTC (rev 1566)
@@ -0,0 +1,143 @@
+<!--
+        Last Changed Date: $LastChangedDate$
+        Last Changed By:   $LastChangedBy$
+        Revision:          $LastChangedRevision$ 
+-->
+
+<sect1 id="hacker-svn" xreflabel="&book-product; Code from SVN">
+<?dbhtml filename="svn.html" dir="hacker"?>
+<title>Code from SVN</title>
+
+<sect2>
+<title>Usage</title>
+
+<para>Before you can follow these instructions, you will need to have
+acquired a copy of the &book-product; source code from the SVN
+repository.  You can get that from <xref linkend="common-svn"/>.</para>
+
+<para>The repository copy of the &book-product; source code does not
+include an executable <filename>configure</filename> script nor a
+<filename>Makefile</filename>. This is by design, as there is a script
+to create them, which ensures that their contents will always be up to
+date with the source tree contents and not require manual
+editing.</para>
+
+<para>&book-product; has been configured to use the GNU
+<filename>autotools</filename> suite for its build process. The build
+system was created using <filename>autoconf-2.57</filename>,
+<filename>automake-1.7.7</filename> and
+<filename>libtool-1.5</filename>.  If you use older versions than those,
+you may experience warnings and/or outright failures
+(<filename>automake-1.6</filename> is known to be unable to handle the
+&book-product; <filename>Makefile.am</filename>) file.</para>
+
+<para>After you checkout the &book-product; source tree, you will need
+to execute :</para>
+
+<screen><command>sh ./bootstrap</command></screen>
+
+<para>in the &book-product; root directory itself. This should result
+output similar to the following:</para>
+
+<screen><command>$ sh ./bootstrap</command>
+You should update your 'aclocal.m4' by running aclocal.
+Putting files in AC_CONFIG_AUX_DIR, `gnubuild'.
+configure.ac: installing 'gnubuild/install-sh'
+configure.ac: installing 'gnubuild/mkinstalldirs'
+configure.ac: installing 'gnubuild/missing'
+Makefile.am: installing 'gnubuild/compile'
+Makefile.am: installing 'gnubuild/depcomp'
+patching file ltmain.sh
+Hunk #1 succeeded at 160 with fuzz 2 (offset -78 lines).
+Hunk #2 succeeded at 269 with fuzz 1.
+Hunk #3 succeeded at 4483 (offset -1172 lines).</screen>
+
+<para>This output comes from the <filename>autoreconf</filename> tool,
+which is part of the <filename>autoconf</filename> package, that
+automatically runs <filename>libtoolize</filename>,
+<filename>autoheader</filename>, <filename>aclocal</filename> and other
+parts of the <filename>autotools</filename> suite. The warning about
+"update your 'aclocal.m4'" can be ignored, as
+<filename>aclocal</filename> is already executed later by
+<filename>autoreconf</filename>. The <filename>patch</filename> offset
+and/or fuzz messages about <filename>ltmain.sh</filename> are caused by
+the <filename>bootstrap</filename> script applying a patch created
+against <filename>libtool-1.5</filename>; if your
+<filename>libtool</filename> version is different, the patch should
+still work correctly, but you may see messages like this from the
+<filename>patch</filename> command. In the worst case, the patch fails
+to apply, the &book-product; build will still be functional, but
+<filename>libtool</filename> will generate more output messages than
+necessary.</para>
+
+<para>Once <filename>bootstrap</filename> has been run, you can execute
+<filename>./configure</filename> like any other GNU autoconf-based package
+to configure &book-product; for your system.</para>
+
+</sect2>
+
+<sect2>
+<title>Editing source files</title>
+
+<para>The &book-product; build system, because it uses
+<filename>automake</filename>, has full dependency tracking on all files
+used to build the binaries. This will reduce your rebuilding time as you
+edit header files and source files, as the make system will know exactly
+what must be rebuilt.</para>
+
+<para>In addition, if you are going to make changes to
+<filename>bootstrap</filename>, you should add the
+<filename>"--enable-maintainer-mode"</filename> parameter to
+your <filename>configure</filename> command. With this done, each time
+you edit and re-run <filename>bootstrap</filename>, the
+<filename>Makefile</filename> will automatically re-run
+<filename>configure</filename> to make your changes take effect. Be
+warned though, that if you manually edit
+<filename>Makefile.am</filename> or <filename>configure.ac</filename>,
+you must modify the <filename>bootstrap</filename> script to incorporate
+your changes, because these files are not stored in the CVS
+repository.</para>
+
+<para>If you add any C source files to the tree, you will need to rerun
+the <filename>bootstrap</filename> script to get them included in your
+build.  If you add header files, it is not necessary to rerun the
+<filename>bootstrap</filename> script unless you plan on using "make
+dist" from that same tree, in which case those added headers would not
+get included into the tarball.</para>
+
+<para>If you add or remove "syntax versions" in any of the
+handlers, you must re-run <filename>bootstrap</filename> to get the version
+lists in <filename>Makefile.am</filename> and
+<filename>configure.ac</filename> to incorporate your changes, or you will
+experience unusual build behavior.</para>
+
+<para>If you add or remove any program options in
+<filename>src/options.h</filename>, you must re-run
+<filename>bootstrap</filename> to regenerate
+<filename>src/option-list.h</filename>.  Without that file being
+regenerated, you may experience compile errors or find that your newly
+added option does not work properly.</para>
+
+<para>All other types of files fall into two categories:</para>
+
+<blockquote><para>those that should be present 
+<emphasis role="bold">only</emphasis> in the CVS repository</para>
+</blockquote>
+
+<para>Nothing needs to be done for these files, other than the relevant
+"cvs add" commands.</para>
+
+<blockquote><para>those that should be added to the distribution
+tarball</para></blockquote>
+
+<para>The <filename>bootstrap.Makefile</filename> script will need to be
+edited, specifically the line that sets <filename>EXTRA_DIST</filename>
+near the beginning of the script. Add the path(s) to the new files to this
+line, or add an additional line starting with "<filename>EXTRA_DIST
++=</filename>" (standard GNU makefile syntax). If the files are not
+listed on this line, they will not be included in the tarball created by
+<command>make dist</command>.</para>
+
+</sect2>
+
+</sect1>

Modified: nALFS/hackers_guide/trunk/part2/part2.ent
===================================================================
--- nALFS/hackers_guide/trunk/part2/part2.ent	2004-10-13 03:02:20 UTC (rev 1565)
+++ nALFS/hackers_guide/trunk/part2/part2.ent	2004-10-15 02:52:14 UTC (rev 1566)
@@ -7,11 +7,11 @@
 <!ENTITY part2                  SYSTEM "part2.xml">
 
 <!ENTITY common-common          SYSTEM "common/common.xml">
-<!ENTITY common-cvs             SYSTEM "common/cvs.xml">
+<!ENTITY common-svn             SYSTEM "common/svn.xml">
 <!ENTITY common-bugzilla        SYSTEM "common/bugzilla.xml">
 
 <!ENTITY hacker-hacker          SYSTEM "hacker/hacker.xml">
 <!ENTITY hacker-prereqs         SYSTEM "hacker/prereqs.xml">
 <!ENTITY hacker-coding-style    SYSTEM "hacker/coding_style.xml">
 <!ENTITY hacker-distro-tarballs SYSTEM "hacker/distro_tarballs.xml">
-
+<!ENTITY hacker-svn             SYSTEM "hacker/svn.xml">




More information about the alfs-log mailing list