# OpenSS7 Linux Fast STREAMS -- CVS procedures.  2006-01-03
# README-cvs,v 0.9.2.5 2006/01/03 16:21:41 brian Exp
# Copyright (c) 2001-2006  OpenSS7 Corporation. <http://www.openss7.com/>
# Copyright (c) 1997-2000  Brian Bidulock <bidulock@openss7.org>
# See the end for copying conditions.

The following is an extract from the manual to assist CVS developers:

6.1.6 Downloading from CVS
--------------------------

If you are a subscriber or sponsor of The OpenSS7 Project
(http://www.openss7.org/) with CVS archive access privileges then you can
download release or mid-release versions of the `streams' package from the
project CVS archive.

The Linux Fast-STREAMS package is located in the `streams' subdirectory of
`/var/cvs'.  For release tag information, see *Note Releases::.

To access the archive from the project CVS pserver, use the following commands
to check out a version from the archive:

     % export CVSROOT='-d:pserver:USERNAME@cvs.openss7.com:2401/var/cvs'
     % cvs login
     Password: *********
     % cvs co -r streams_0.7a.4 streams
     % cvs logout

It is, of course, possible to check out by date or by other criteria.  For more
information, see *Note cvs(1): (*manpages*)cvs(1).

 Preparing the CVS Working Directory
....................................

Although public releases of the `streams' package do not require
reconfiguration, creating a configurable directory from the CVS archive
requires tools not normally distributed with the other releases.

The build host requires the following GNU tools:

   * `autoconf 2.59'

   * `automake 1.9.5'

   * `libtool 1.5.14'

   * `gettext 0.14.1'

   * `texinfo 4.6'

It should be stressed that, in particular, the `autoconf' and `automake' must
be at version releases `2.59' and `1.9'.  _The versions normally distributed in
mainstream GNU/Linux distributions are, in fact, much older than these
versions._(1)  GNU version of these packages configured and installed to default
directories will install in `/usr/local/' allowing them to coexist with
distribution installed versions.

In addition, the build host requires a complete tool chain for compiling for the
target host, including kernel tools such as `genksyms' and others.

To generate a configuration script and the necessary scriptlets required by the
GNU autoconf system, execute the following commands on the working directory:

     % autoreconf -fiv streams

where, `streams' is the name of the directory to where the working copy was
checked out under the previous step.  This command generates the `configure'
script and other missing pieces that are normally distributed with the release
Tar Balls, SRPMs and DSCs.

Make sure that `autoreconf --version' returns `2.59'.  Otherwise, you may need
to perform something like the following:

     % PATH="/usr/local/bin:$PATH"
     % autoreconf -fiv streams

After reconfiguring the directory, the package can then be configured and built
using the same instructions as are used for the Tar Ball, see *Note Configuring
the Tar Ball::, and *Note Building from the Tar Ball::.

Do note, however, that `make' will rebuild the documentation that is normally
released with the package.  Additional tools may be necessary for building the
documentation.

When configuring the package in a working directory and while working a
change-compile-test cycle that involves configuration macros or documentation, I
find it of great advantage to invoke the GNU `configure' options
`--enable-maintainer-mode' and `--enable-dependency-tracking'.  The first of
these two options will add maintainer-specific targets to any generated
`Makefile', and the later will invoke automatic dependency tracking within the
`Makefile' so rebuilds after changes to macro, source or documentation files
will be automatically rebuilt.

---------- Footnotes ----------

(1) A notable exception is Debian.



=========================================================================

Copyright (c) 2001-2006  OpenSS7 Corporation. <http://www.openss7.com/>
Copyright (c) 1997-2000  Brian Bidulock <bidulock@openss7.org>

All Rights Reserved.

 Permission is granted to make and distribute verbatim copies of this
 manual provided the copyright notice and this permission notice are
 preserved on all copies.

 Permission is granted to copy and distribute modified versions of this
 manual under the conditions for verbatim copying, provided that the
 entire resulting derived work is distributed under the terms of a
 permission notice identical to this one

 Since the Linux kernel and libraries are constantly changing, this
 manual page may be incorrect or out-of-date.  The author(s) assume no
 responsibility for errors or omissions, or for damages resulting from
 the use of the information contained herein.  The author(s) may not
 have taken the same level of care in the production of this manual,
 which is licensed free of charge, as they might when working
 professionally.

 Formatted or processed versions of this manual, if unaccompanied by
 the source, must acknowledge the copyright and authors of this work.

-------------------------------------------------------------------------

 U.S. GOVERNMENT RESTRICTED RIGHTS.  If you are licensing this Software
 on behalf of the U.S. Government ("Government"), the following
 provisions apply to you.  If the Software is supplied by the Department
 of Defense ("DoD"), it is classified as "Commercial Computer Software"
 under paragraph 252.227-7014 of the DoD Supplement to the Federal
 Acquisition Regulations ("DFARS") (or any successor regulations) and the
 Government is acquiring only the license rights granted herein (the
 license rights customarily provided to non-Government users).  If the
 Software is supplied to any unit or agency of the Government other than
 DoD, it is classified as "Restricted Computer Software" and the
 Government's rights in the Software are defined in paragraph 52.227-19
 of the Federal Acquisition Regulations ("FAR") (or any successor
 regulations) or, in the cases of NASA, in paragraph 18.52.227-86 of the
 NASA Supplement to the FAR (or any successor regulations).

=========================================================================

 Commercial licensing and support of this software is available from
 OpenSS7 Corporation at a fee.  See http://www.openss7.com/

=========================================================================
