
This is a port of CVS 1.11.23 to MSDOS/DJGPP.

  CVS is a version control system, which allows you to keep old versions
  of files (usually source code), keep a log of who, when, and why changes
  occurred, etc.  It handles multiple developers, multiple directories,
  triggers to enable/log/control various operations, and can work over a
  wide area network.


  IMPORTANT: CVS uses many filenames for its files that are invalid under
  MS-DOS.  You will need LFN support to run this program under plain DOS.
  It is very unlikely that it may be possible to port this program to a
  SFN OS without breaking the complete code.  I will certainly not try.



1.:     DJGPP specific changes.
        =======================

      - The source archives that have been used to create this port can be
        downloaded as:
          ftp://ftp.gnu.org/gnu/non-gnu/cvs/source/stable/1.11.23/cvs-1.11.23.tar.bz2
          http://www.zlib.net/zlib-1.2.11.tar.gz

      - To install, configure, compile and use this port you will need LFN
        support.  There is no way to use the cvs program WITHOUT LFN support.

      - The zlib included in the sources has been replaced with the latest
        DJGPP port of zlib.

      - Where it was appropriate the diff programs code provided by the
        sources has been modified according to the changes done to the
        latest DJGPP port of diffutils.

      - The port has been comfigured and compiled to use "edit" as default
        editor.  You can specify some other editor by setting the CVSEDITOR
        environment variable.  Please note that only for edit all slashes
        in the path of the file name are converted into backslashes.  This
        means that no other editor that requires backslashes in the paths
        is supported.

      - This port can be compiled using the latest version of the GDBM port
        instead of the included data base routines.  What data base will be
        used when the sources are configured and compiled can be selected as
        flags passed to config.bat:
          1) config.bat  ndbm
          will make that the binary is compiled using the ndbm library
          provided by the latest DJGPP port of gdbm.
          2) config.bat  gdbm
          will make that the binary is compiled using the gdbm library
          provided by the latest DJGPP port of gdbm.
          3) If neither ndbm  nor gdbm is passed as flag to config.bat
          then the data base functions provided by the CVS sources will
          be used.  This is the way the binary has been compiled.
        I have developt this port for gdbm111 and I have neither tested
        it for any previous nor later version of this port.
        It must be clear that if repositories shall be shared between
        different CVS programs they must all use the same data base program
        so the best is to use CVS's own data base code.

      - This port will look for the global configuration file (aka .cvsrc)
        at the home directory of the user by evaluating the $HOME environment
        variable.  If it is not set it will look at /dev/env/DJDIR and at the
        directory where the cvs program is stored.  In that order.

      - CVS uses its own routines instead of an external RCS, so none of the
        extensions of the DJGPP port of RCS will work.

      - All files are treated as text by default. If you want to put a binary
        file in a CVS repository, you should always use the -kb option when
        adding/importing those files. You can use this same method to add Unix-
        style text files, but do note that -kb disables RCS keyword expansion,
        which may not be what you want.
        For more information, see the 'Binary files' topic in the CVS Info file.

      - Only local CVSRoots are supported.  This port of CVS can not act as a
        server, nor can it act as a client to a CVS server.  Neither kerberos
        nor ssh ports for DJGPP are available so it is unlikely that in the
        near future a DJGPP port of CVS that provides this functionality will
        be available.

      - Probably none of the scripts stored in the /contribute directory will
        work under DOS.  This should not be an issue because almost all programs
        required by these scripts have also not been ported to DOS yet, thus
        they are all of no use on DOS.

      - The port has been configured and compiled on Win98SE, MS-DOS 7.10
        using DOSLFN 0.41c and MS-DOS 6.22 using DOSLFN 0.41c.  There is
        absolute no guarantee that this may be possible with any other DOS-
        like OS.  Due to the use of long file names it will not be possible
        to configure and compile without LFN support.

      - This version of the port has been compiled using gcc346 and bnu234b.

        As usual, all djgpp specific files (config.bat, diffs, readme files,
        etc.) are located in the djgpp subdir.

        For further information about CVS please read the info docs and NEWS file.


2.:     Installing the binary package.
        ==============================

2.1.:   Copy the binary distribution into the top DJGPP installation directory
        and unzip it running *ONE* of the following commands:
          unzip32 cvs111b.zip      or
          djtarx cvs111b.zip       or
          pkunzip -d cvs111b.zip


3.:     Building the binaries from sources.
        ===================================

3.1.:   Create a temporary directory and copy the source package into the
        directory.  If you download the source distribution from one of the
        DJGPP sites, just unzip it preserving the directory structure
        running *ONE* of the following commands:
          unzip32 cvs111s.zip      or
          djtarx cvs111s.zip       or
          pkunzip -d cvs111s.zip

3.2.:   To build the binaries you will need the following binary packages:
          djdev205.zip (or a later but NOT a prior version)
          bsh205bbr3.zip (or a later but NOT a prior version)
          gccNNNb.zip, bnuNNNb.zip, makNNNb.zip, filNNNb.zip, shlNNNb.zip,
          txtNNNb.zip, txiNNNb.zip, grepNNNb.zip, sedNNNb.zip, mktmpNNb.zip
          and difNNNb.zip.

        NNN represents the latest version number of the binary packages.  All
        this packages can be found in the /v2gnu directory of any
        ftp.delorie.com mirror.
        You will need bsh205bbr3.zip or later and *NOT* a prior version or
        the build will fail.  The same applies to djdev205.zip.

3.3.:   The package has been configured to be build in a separate build directory
        under the top srcdir (aka cvs-1.11.23).  To build the binaries cd
        into /_build directory.  If for some reason you want to reconfigure the
        package cd into the build directory and run the following commands:
          del config.cache
          make clean
          ..\djgpp\config ./..

        Please note that you *MUST* delete the config.cache file in the "_build"
        directory or you will not really reconfigure the sources because the
        configuration informations will be read from the cache file instead
        of being newly computed.

        config.bat, among other things, will start the configure script passing
        to it a couple of arguments.  You can control these argument passing the
        following command line arguments to config.bat:
          nls or no-nls, default nls.  NLS support enabled.
          cache or no-cache, default cache.  Cache in build directory.
          dep or no-dep, default no-dep.  No dependency tracking.
          ndbm or no-ndbm, default no-ndbm.  Use the ndbm support provided by
                                             cvs and not the system one.
          gdbm or no-gdbm, default no-gdbm.  Use the ndbm support provided by
                                             cvs and not gdbm from the system.
        All other configure specific options are not set by config.bat so their
        values are left as they are.  If no arguments are passed to config.bat
        then the default values are used.


        To build the programs in a directory other than where the sources are,
        you must add the parameter that specifies the source directory,
        e.g:
          x:\src\contrib\cvs-1.11.23\djgpp\config x:/src/contrib/cvs-1.11.23

        Lets assume you want to build the binaries in a directory placed on a
        different drive (z:\build in this case) from where the sources are,
        then you will run the following commands:
          z:
          md \build
          cd \build
          x:\src\contrib\cvs-1.11.23\djgpp\config x:/src/contrib/cvs-1.11.23

        The order of the options and the srcdir option does not matter.  You
        *MUST* use forward slashes to specify the source directory.

        The batch file will set same environment variables, make MSDOS specific
        modifications to the Makefile.in's and supply all other needed options
        to the configure script.

3.4.:   To compile the package run from the directory where you have configured
        the sources the command:
          make

3.5.:   Now you can run the tests if you like. From the directory where you have
        configured the sources run the command:
          make check

        Neither the gnulib specific checks nor the CVS specific checks will work.
        This is because the gnulib checks have never been ported to DJGPP and
        never will be.  Concerning the CVS checks, they check the server and
        client capabilities and none of them have been ported.
        The only way to test this port is by using it.

3.6.:   To install the binary, info docs and man pages run the following command
        from the directory where you have configured the sources:
          make install

        This will install the products into your DJGPP installation tree given
        by the default prefix "/dev/env/DJDIR".  If you prefer to install them
        into some other directory you will have to set prefix to the appropriate
        value:
          make install prefix=z:/some/other/place



        Send CVS specific bug reports to <bug-cvs@nongnu.org>.
        Send suggestions and bug reports concerning the DJGPP port to
        comp.os.msdos.djgpp or <djgpp@delorie.com>.


Enjoy.

          Guerrero, Juan Manuel <juan.guerrero@gmx.de>
