CVS source control tool - Unix

This is a discussion on CVS source control tool - Unix ; I have compiled CVS on Sun Solaris 8. I use cvs commit file_name, but could not check in file. This is the first time I use CVS. Thanks...

+ Reply to Thread
Results 1 to 9 of 9

Thread: CVS source control tool

  1. CVS source control tool

    I have compiled CVS on Sun Solaris 8.
    I use cvs commit file_name, but could not check in file.
    This is the first time I use CVS.

    Thanks


  2. Re: CVS source control tool

    blackdog wrote:
    > I have compiled CVS on Sun Solaris 8.
    > I use cvs commit file_name, but could not check in file.
    > This is the first time I use CVS.
    >
    > Thanks
    >


    You may have compiled CVS but have you actually installed it and set it up on the server ?
    This could be so many things !!!!

    I suggest your first stop is http://www.cvshome.org there is a very good CVS manual that
    will get you going for both setup and usage (Manual and Documentation and FAQ). You just
    need to do a little bit of reading.

    John.

  3. Re: CVS source control tool

    "blackdog" writes:
    > I have compiled CVS on Sun Solaris 8.
    > I use cvs commit file_name, but could not check in file.
    > This is the first time I use CVS.


    Before you check in a file, you have to set up a "repository" and then
    point cvs(1) to it, either through a command line option or the CVSROOT
    environment variable.

    The home page of CVS has many good pointers to documentation about the
    use of CVS. Point your favorite browser to

    https://www.cvshome.org/docs/

    and off you go :-)

    As a sidenote:

    If this is the first time you've ever found yourself in need of a
    version control system, then CVS may be just fine. Many large projects
    use CVS for their every day work (i.e. the various open source BSDs).
    There are a few limitations of CVS that may start being annoying after a
    while. It may be a good idea to look at other version control systems
    too, i.e. Subversion, which offer some improvements.

    - Giorgos


  4. Re: CVS source control tool

    I have went through cvshome.org docs, but I could not find a way
    to check in a new file - first time check in.
    I issue a command as below to do the first time check in but fail.
    cvs commit -m file_name


  5. Re: CVS source control tool

    "blackdog" writes:

    > I have went through cvshome.org docs, but I could not find a way
    > to check in a new file - first time check in.
    > I issue a command as below to do the first time check in but fail.
    > cvs commit -m file_name


    Try posting the error message,
    or tell us what you mean by 'it failed'.

    The -m option is followed by the comment, not the filename.

  6. Re: CVS source control tool

    In fact, I was trying to work out subversion, I have done compiling and
    done the db-4.3.28.NC
    Compiling also. But I don't know how the link together to use it.

    Before, I compile the subversion, I did use configure to generate the
    Makefile, but in the
    Log file say:

    You don't seem to have Berkeley DB version 4.0.14 or newer
    installed and linked to APR-UTIL. We have created Makefiles which
    will build without the Berkeley DB back-end; your repositories will
    use FSFS as the default back-end. You can find the latest version of
    Berkeley DB here:
    http://www.sleepycat.com/download/index.shtml

    Any help will be appreciated. tks.


  7. Re: CVS source control tool

    "blackdog" writes:
    > In fact, I was trying to work out subversion, I have done compiling and
    > done the db-4.3.28.NC
    > Compiling also. But I don't know how the link together to use it.
    >
    > Before, I compile the subversion, I did use configure to generate the
    > Makefile, but in the
    > Log file say:
    >
    > You don't seem to have Berkeley DB version 4.0.14 or newer
    > installed and linked to APR-UTIL. We have created Makefiles which
    > will build without the Berkeley DB back-end; your repositories will
    > use FSFS as the default back-end. You can find the latest version of
    > Berkeley DB here:
    > http://www.sleepycat.com/download/index.shtml
    >
    > Any help will be appreciated. tks.


    Berkeley DB support is not mandatory. You can always use the "FSFS"
    repository type of Subversion.


  8. Re: CVS source control tool

    "blackdog" writes:
    > I have went through cvshome.org docs, but I could not find a way
    > to check in a new file - first time check in.
    > I issue a command as below to do the first time check in but fail.
    > cvs commit -m file_name


    a. The initial "revision" of a file is not committed.

    It's either "added" to a checked out working copy or "imported" from an
    unversioned tree into a repository.

    b. The argument of the -m option is the filename above. This is wrong.


  9. Re: CVS source control tool

    blackdog wrote:
    > I have compiled CVS on Sun Solaris 8.
    > I use cvs commit file_name, but could not check in file.
    > This is the first time I use CVS.
    >
    > Thanks
    >

    I highly recommend you read this book

    http://cvsbook.red-bean.com/

    Best Regards

    --Duane Whitty

+ Reply to Thread