David Summers <david@summersoft.fay.ar.us> writes:
> The following patch details instructions for bootstrapping from RPMs and
> building source from RPMS source or directly from the working copy.
>
> Please let me know what changes need to be made.
Gack -- it still doesn't apply, apparently INSTALL has changed since
then.
I have a better idea. Just commit the change, and it can be reviewed
in place. It's not like INSTALL can break the build or anything. If
for some reason there's a problem (seems unlikely), it's easy enough
to revert the change until you get a chance to redo it.
-Karl
> Index: ./INSTALL
> ===================================================================
> --- ./.svn/text-base/INSTALL.svn-base Sat Dec 15 13:38:43 2001
> +++ ./INSTALL Sat Dec 15 18:14:31 2001
> @@ -50,94 +50,157 @@
>
> III. INSTALLATION
>
> - A. BOOTSTRAPPING FROM TARBALL
> + A. BOOTSTRAPPING FROM TARBALL OR RPM
>
> In order to get the latest Subversion source code, you need to
> check it out of a Subversion repository, and thus need a working
> Subversion client.
>
> - Download the latest distribution tarball from:
>
> - http://subversion.tigris.org/servlets/ProjectDownloadList
> + 1. BOOTSTRAPPING FROM TARBALL
>
> - Unpack this tarball, and use the standard GNU procedure to compile:
> + Download the latest distribution tarball from:
>
> - $ ./configure --enable-maintainer-mode --disable-shared
> - $ make
> + http://subversion.tigris.org/servlets/ProjectDownloadList
>
> - (The first switch to ./configure turns on debugging, and the
> - second switch builds a statically-linked client binary.)
> + Unpack this tarball, and use the standard GNU procedure to compile:
>
> - After compiling, you will have a large 'svn' binary sitting in
> - the tree. Use it to check out a real Subversion working copy:
> + $ ./configure --enable-maintainer-mode --disable-shared
> + $ make
>
> - $ subversion/clients/cmdline/svn checkout \
> - http://svn.collab.net/repos/svn/trunk -d svn
> + (The first switch to ./configure turns on debugging, and the
> + second switch builds a statically-linked client binary.)
>
> - A svn/dist.sh
> - A svn/buildcheck.sh
> - A svn/HACKING
> - ...
> + After compiling, you will have a large 'svn' binary sitting in
> + the tree. Use it to check out a real Subversion working copy:
>
> - B. BUILDING THE LATEST SOURCE
> + $ subversion/clients/cmdline/svn checkout \
> + http://svn.collab.net/repos/svn/trunk -d svn
>
> - You can discard the directory created by the tarball; you're
> - about to build the latest, greatest Subversion client.
> + A svn/dist.sh
> + A svn/buildcheck.sh
> + A svn/HACKING
> + ...
>
> - First off, if you have any Subversion libraries lying around
> - from previous 'make installs', clean them up first!
> + 2. BOOTSTRAPPING FROM RPM
>
> - # rm -f /usr/local/lib/libsvn*
> - # rm -f /usr/local/lib/libapr*
> - # rm -f /usr/local/lib/libexpat*
> - # rm -f /usr/local/lib/libneon*
> + If you are using Linux (or any OS that can use RPM) then another
> + possibility is to download the binary RPM from the
> + http://summersoft.fay.ar.us/pub/linux/RPMS/i386 or
> + http://summersoft.fay.ar.us/pub/linux/RPMS/ppc directory.
> + Currently only Linux on the i386 and ppc platforms are supported
> + using this method. You might also require other RPMS to use the
> + subversion RPM depending on what packages you already have installed:
>
> - Start the process by running "autogen.sh":
> + subversion*.i386.rpm
> + apr*.i386.rpm (Version 0.2001.10.24 or greater)
> + db3*.i386.rpm (Version 3.3.11 or greater)
> + expat (Comes with RedHat)
> + neon (Version 0.17.2 or greater)
>
> - $ chmod +x autogen.sh # if not already executable
> - $ ./autogen.sh
> + After downloading, install it:
>
> - This script will make sure you have all the necessary components
> - available to build Subversion. If any are missing, you will be
> - told where to get them from. (See the 'requirements' section
> - further down.)
> + rpm -ivh subversion*.i386.rpm (add other packages as necessary)
>
> - After all components are in place, follow the usual procedure:
> + After installing you can then use the svn command to check out the
> + latest source code:
>
> - $ ./configure --enable-maintainer-mode --disable-shared
> - $ make
> - $ make check (optional)
> - # make install
> + $ /usr/bin/svn checkout http://svn.collab.net/repos/svn/trunk -d svn
>
> - The flags to `configure' are highly recommended for developers,
> - as they build a statically-linked binary. If you don't use
> - those flags, then you must reverse the order of the "make check"
> - and "make install" steps, because the shared libraries must be
> - installed before "make check" will work.
> + A svn/dist.sh
> + A svn/buildcheck.sh
> + A svn/HACKING
> + ...
>
> - Additionally, with shared library builds, the destination
> - library directory must be listed in either /etc/ld.so.conf or
> - $LD_LIBRARY_PATH (for linux systems), so that Subversion will be
> - able to dynamically load repository access plugins. If you try
> - to do a checkout and see an error like:
>
> - svn_error: #21068 : <Bad URL passed to RA layer>
> - Unrecognized URL scheme: http://svn.collab.net/repos/svn/trunk
> + B. BUILDING THE LATEST SOURCE TARBALL OR SOURCE RPM
>
> - It probably means that the dynamic loader/linker can't find all
> - of the libsvn_* libraries.
> + 1. BUILDING FROM SOURCE TARBALL
> + You can discard the directory created by the tarball; you're
> + about to build the latest, greatest Subversion client.
>
> - Note that if you commonly build with the -jN option to make, the
> - make step above may fail, because we don't ensure that third
> - party libraries in our source tree will finish building before
> - subversion itself. If you want to use -jN, use the following
> - instead:
> + First off, if you have any Subversion libraries lying around
> + from previous 'make installs', clean them up first!
>
> - $ ./configure --enable-maintainer-mode --disable-shared
> - $ make -jN external-all
> - $ make -jN local-all
> - $ make check
> - # make install
> + # rm -f /usr/local/lib/libsvn*
> + # rm -f /usr/local/lib/libapr*
> + # rm -f /usr/local/lib/libexpat*
> + # rm -f /usr/local/lib/libneon*
> +
> + Start the process by running "autogen.sh":
> +
> + $ chmod +x autogen.sh # if not already executable
> + $ ./autogen.sh
> +
> + This script will make sure you have all the necessary components
> + available to build Subversion. If any are missing, you will be
> + told where to get them from. (See the 'requirements' section
> + further down.)
> +
> + After all components are in place, follow the usual procedure:
> +
> + $ ./configure --enable-maintainer-mode --disable-shared
> + $ make
> + $ make check (optional)
> + # make install
> +
> + The flags to `configure' are highly recommended for developers,
> + as they build a statically-linked binary. If you don't use
> + those flags, then you must reverse the order of the "make check"
> + and "make install" steps, because the shared libraries must be
> + installed before "make check" will work.
> +
> + Additionally, with shared library builds, the destination
> + library directory must be listed in either /etc/ld.so.conf or
> + $LD_LIBRARY_PATH (for linux systems), so that Subversion will be
> + able to dynamically load repository access plugins. If you try
> + to do a checkout and see an error like:
> +
> + svn_error: #21068 : <Bad URL passed to RA layer>
> + Unrecognized URL scheme: http://svn.collab.net/repos/svn/trunk
> +
> + It probably means that the dynamic loader/linker can't find all
> + of the libsvn_* libraries.
> +
> + Note that if you commonly build with the -jN option to make, the
> + make step above may fail, because we don't ensure that third
> + party libraries in our source tree will finish building before
> + subversion itself. If you want to use -jN, use the following
> + instead:
> +
> + $ ./configure --enable-maintainer-mode --disable-shared
> + $ make -jN external-all
> + $ make -jN local-all
> + $ make check
> + # make install
> +
> + 2. BUILDING FROM SOURCE RPM
> +
> + The following has only been tested on RedHat Linux 7.1 and 7.2 and
> + PPC Linux.
> +
> + Download the latest subversion source RPM from the
> + http://summersoft.fay.ar.us/pub/linux/RPMS/src directory.
> +
> + Additional Requirements (RPM package can also be found in the same
> + directory):
> +
> + apache (Version 2.0.16 or greater) (ONLY NEEDED for SVN SERVER)
> + apr-devel (Version 0.2001.10.24 or greater)
> + autoconf (Version 2.52 or greater)
> + db3-devel (Version 3.3.11 or greater)
> + expat-devel (Comes with RedHat)
> + libtool (Version 1.4.2 or greater)
> + neon (Version 0.17.2)
> + python (Version 1.5 or greater or 2.0 or greater for testing)
> +
> + To build Subversion make sure that the previous requirments are met
> + and type the command:
> +
> + rpm -ba subversion*src.rpm
> +
> + This should build the binary subversion, subversion-server and
> + subversion-devel packages.
>
>
> C. BUILD REQUIREMENTS
> @@ -311,6 +374,10 @@
>
> V. BUILDING A SUBVERSION SERVER
>
> + (Following the RPM Binary install or RPM Source install procedures above
> + will build a SUBVERSION server for Linux RedHat 7.1, 7.2, and PPC Linux
> + systems *IF* the apache-devel-2.0.16 or greater package is already
> + installed when the SUBVERSION RPM is built.)
>
> 1. Checkout the "httpd-2.0" cvs module from apache.org. Put it
> whereever you wish; it's an independent project.
>
>
> On 23 Jan 2002, Ben Collins-Sussman wrote:
>
> > Date: 23 Jan 2002 14:48:54 -0600
> > From: Ben Collins-Sussman <sussman@collab.net>
> > To: David Summers <david@summersoft.fay.ar.us>
> > Subject: Re: [David Summers <david@summersoft.fay.ar.us>] RPM
> > documentation in INSTALL file.
> >
> >
> > David, apologies for letting this patch sit around so long. The
> > problem is that it no longer cleanly applies. Can I ask you to resend
> > it against the latest INSTALL file?
> >
> >
> >
> > > How is this for a first start at documenting RPM binary and source and
> > > bootstrapping? Does anything need to be added, changed, deleted, or
> > > clarified?
> > >
> > > Log:
> > > ================
> > >
> > > * ./INSTALL : Added RPM binary and source bootstrap information to the
> > > INSTALL file.
> > > ================
> > > Index: ./INSTALL
> > > ===================================================================
> > > --- ./.svn/text-base/INSTALL.svn-base Sat Dec 15 13:38:43 2001
> > > +++ ./INSTALL Sat Dec 15 18:14:31 2001
> > > @@ -50,94 +50,157 @@
> > >
> > > III. INSTALLATION
> > >
> > > - A. BOOTSTRAPPING FROM TARBALL
> > > + A. BOOTSTRAPPING FROM TARBALL OR RPM
> > >
> > > In order to get the latest Subversion source code, you need to
> > > check it out of a Subversion repository, and thus need a working
> > > Subversion client.
> > >
> > > - Download the latest distribution tarball from:
> > >
> > > - http://subversion.tigris.org/servlets/ProjectDownloadList
> > > + 1. BOOTSTRAPPING FROM TARBALL
> > >
> > > - Unpack this tarball, and use the standard GNU procedure to compile:
> > > + Download the latest distribution tarball from:
> > >
> > > - $ ./configure --enable-maintainer-mode --disable-shared
> > > - $ make
> > > + http://subversion.tigris.org/servlets/ProjectDownloadList
> > >
> > > - (The first switch to ./configure turns on debugging, and the
> > > - second switch builds a statically-linked client binary.)
> > > + Unpack this tarball, and use the standard GNU procedure to compile:
> > >
> > > - After compiling, you will have a large 'svn' binary sitting in
> > > - the tree. Use it to check out a real Subversion working copy:
> > > + $ ./configure --enable-maintainer-mode --disable-shared
> > > + $ make
> > >
> > > - $ subversion/clients/cmdline/svn checkout \
> > > - http://svn.collab.net/repos/svn/trunk -d svn
> > > + (The first switch to ./configure turns on debugging, and the
> > > + second switch builds a statically-linked client binary.)
> > >
> > > - A svn/dist.sh
> > > - A svn/buildcheck.sh
> > > - A svn/HACKING
> > > - ...
> > > + After compiling, you will have a large 'svn' binary sitting in
> > > + the tree. Use it to check out a real Subversion working copy:
> > >
> > > - B. BUILDING THE LATEST SOURCE
> > > + $ subversion/clients/cmdline/svn checkout \
> > > + http://svn.collab.net/repos/svn/trunk -d svn
> > >
> > > - You can discard the directory created by the tarball; you're
> > > - about to build the latest, greatest Subversion client.
> > > + A svn/dist.sh
> > > + A svn/buildcheck.sh
> > > + A svn/HACKING
> > > + ...
> > >
> > > - First off, if you have any Subversion libraries lying around
> > > - from previous 'make installs', clean them up first!
> > > + 2. BOOTSTRAPPING FROM RPM
> > >
> > > - # rm -f /usr/local/lib/libsvn*
> > > - # rm -f /usr/local/lib/libapr*
> > > - # rm -f /usr/local/lib/libexpat*
> > > - # rm -f /usr/local/lib/libneon*
> > > + If you are using Linux (or any OS that can use RPM) then another
> > > + possibility is to download the binary RPM from the
> > > + http://summersoft.fay.ar.us/pub/linux/RPMS/i386 or
> > > + http://summersoft.fay.ar.us/pub/linux/RPMS/ppc directory.
> > > + Currently only Linux on the i386 and ppc platforms are supported
> > > + using this method. You might also require other RPMS to use the
> > > + subversion RPM depending on what packages you already have installed:
> > >
> > > - Start the process by running "autogen.sh":
> > > + subversion*.i386.rpm
> > > + apr*.i386.rpm (Version 0.2001.10.24 or greater)
> > > + db3*.i386.rpm (Version 3.3.11 or greater)
> > > + expat (Comes with RedHat)
> > > + neon (Version 0.17.2 or greater)
> > >
> > > - $ chmod +x autogen.sh # if not already executable
> > > - $ ./autogen.sh
> > > + After downloading, install it:
> > >
> > > - This script will make sure you have all the necessary components
> > > - available to build Subversion. If any are missing, you will be
> > > - told where to get them from. (See the 'requirements' section
> > > - further down.)
> > > + rpm -ivh subversion*.i386.rpm (add other packages as necessary)
> > >
> > > - After all components are in place, follow the usual procedure:
> > > + After installing you can then use the svn command to check out the
> > > + latest source code:
> > >
> > > - $ ./configure --enable-maintainer-mode --disable-shared
> > > - $ make
> > > - $ make check (optional)
> > > - # make install
> > > + $ /usr/bin/svn checkout http://svn.collab.net/repos/svn/trunk -d svn
> > >
> > > - The flags to `configure' are highly recommended for developers,
> > > - as they build a statically-linked binary. If you don't use
> > > - those flags, then you must reverse the order of the "make check"
> > > - and "make install" steps, because the shared libraries must be
> > > - installed before "make check" will work.
> > > + A svn/dist.sh
> > > + A svn/buildcheck.sh
> > > + A svn/HACKING
> > > + ...
> > >
> > > - Additionally, with shared library builds, the destination
> > > - library directory must be listed in either /etc/ld.so.conf or
> > > - $LD_LIBRARY_PATH (for linux systems), so that Subversion will be
> > > - able to dynamically load repository access plugins. If you try
> > > - to do a checkout and see an error like:
> > >
> > > - svn_error: #21068 : <Bad URL passed to RA layer>
> > > - Unrecognized URL scheme: http://svn.collab.net/repos/svn/trunk
> > > + B. BUILDING THE LATEST SOURCE TARBALL OR SOURCE RPM
> > >
> > > - It probably means that the dynamic loader/linker can't find all
> > > - of the libsvn_* libraries.
> > > + 1. BUILDING FROM SOURCE TARBALL
> > > + You can discard the directory created by the tarball; you're
> > > + about to build the latest, greatest Subversion client.
> > >
> > > - Note that if you commonly build with the -jN option to make, the
> > > - make step above may fail, because we don't ensure that third
> > > - party libraries in our source tree will finish building before
> > > - subversion itself. If you want to use -jN, use the following
> > > - instead:
> > > + First off, if you have any Subversion libraries lying around
> > > + from previous 'make installs', clean them up first!
> > >
> > > - $ ./configure --enable-maintainer-mode --disable-shared
> > > - $ make -jN external-all
> > > - $ make -jN local-all
> > > - $ make check
> > > - # make install
> > > + # rm -f /usr/local/lib/libsvn*
> > > + # rm -f /usr/local/lib/libapr*
> > > + # rm -f /usr/local/lib/libexpat*
> > > + # rm -f /usr/local/lib/libneon*
> > > +
> > > + Start the process by running "autogen.sh":
> > > +
> > > + $ chmod +x autogen.sh # if not already executable
> > > + $ ./autogen.sh
> > > +
> > > + This script will make sure you have all the necessary components
> > > + available to build Subversion. If any are missing, you will be
> > > + told where to get them from. (See the 'requirements' section
> > > + further down.)
> > > +
> > > + After all components are in place, follow the usual procedure:
> > > +
> > > + $ ./configure --enable-maintainer-mode --disable-shared
> > > + $ make
> > > + $ make check (optional)
> > > + # make install
> > > +
> > > + The flags to `configure' are highly recommended for developers,
> > > + as they build a statically-linked binary. If you don't use
> > > + those flags, then you must reverse the order of the "make check"
> > > + and "make install" steps, because the shared libraries must be
> > > + installed before "make check" will work.
> > > +
> > > + Additionally, with shared library builds, the destination
> > > + library directory must be listed in either /etc/ld.so.conf or
> > > + $LD_LIBRARY_PATH (for linux systems), so that Subversion will be
> > > + able to dynamically load repository access plugins. If you try
> > > + to do a checkout and see an error like:
> > > +
> > > + svn_error: #21068 : <Bad URL passed to RA layer>
> > > + Unrecognized URL scheme: http://svn.collab.net/repos/svn/trunk
> > > +
> > > + It probably means that the dynamic loader/linker can't find all
> > > + of the libsvn_* libraries.
> > > +
> > > + Note that if you commonly build with the -jN option to make, the
> > > + make step above may fail, because we don't ensure that third
> > > + party libraries in our source tree will finish building before
> > > + subversion itself. If you want to use -jN, use the following
> > > + instead:
> > > +
> > > + $ ./configure --enable-maintainer-mode --disable-shared
> > > + $ make -jN external-all
> > > + $ make -jN local-all
> > > + $ make check
> > > + # make install
> > > +
> > > + 2. BUILDING FROM SOURCE RPM
> > > +
> > > + The following has only been tested on RedHat Linux 7.1 and 7.2 and
> > > + PPC Linux.
> > > +
> > > + Download the latest subversion source RPM from the
> > > + http://summersoft.fay.ar.us/pub/linux/RPMS/src directory.
> > > +
> > > + Additional Requirements (RPM package can also be found in the same
> > > + directory):
> > > +
> > > + apache (Version 2.0.16 or greater) (ONLY NEEDED for SVN SERVER)
> > > + apr-devel (Version 0.2001.10.24 or greater)
> > > + autoconf (Version 2.52 or greater)
> > > + db3-devel (Version 3.3.11 or greater)
> > > + expat-devel (Comes with RedHat)
> > > + libtool (Version 1.4.2 or greater)
> > > + neon (Version 0.17.2)
> > > + python (Version 1.5 or greater or 2.0 or greater for testing)
> > > +
> > > + To build Subversion make sure that the previous requirments are met
> > > + and type the command:
> > > +
> > > + rpm -ba subversion*src.rpm
> > > +
> > > + This should build the binary subversion, subversion-server and
> > > + subversion-devel packages.
> > >
> > >
> > > C. BUILD REQUIREMENTS
> > > @@ -311,6 +374,10 @@
> > >
> > > V. BUILDING A SUBVERSION SERVER
> > >
> > > + (Following the RPM Binary install or RPM Source install procedures above
> > > + will build a SUBVERSION server for Linux RedHat 7.1, 7.2, and PPC Linux
> > > + systems *IF* the apache-devel-2.0.16 or greater package is already
> > > + installed when the SUBVERSION RPM is built.)
> > >
> > > 1. Checkout the "httpd-2.0" cvs module from apache.org. Put it
> > > whereever you wish; it's an independent project.
> > >
> > >
> > >
> > > --
> > > David Wayne Summers "Linux: Because reboots are for upgrades!"
> > > david_at_summersoft.fay.ar.us PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt
> > > PGP Key fingerprint = C0 E0 4F 50 DD A9 B6 2B 60 A1 31 7E D2 28 6D A8
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> > > For additional commands, e-mail: dev-help@subversion.tigris.org
> > >
> > >
> > > ----------
> >
>
> --
> David Wayne Summers "Linux: Because reboots are for upgrades!"
> david_at_summersoft.fay.ar.us PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt
> PGP Key fingerprint = C0 E0 4F 50 DD A9 B6 2B 60 A1 31 7E D2 28 6D A8
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:59 2006