Setting Up Cvs On A Sun Unix System Details needed

Can anyone point me to some documentation that details me on setup of a CVS server?

 

I need to setup a CVS repository on a Sun Unix system with following specs:

 

Machine hardware: sun4v

OS version: 5.10

Processor type: sparc

Hardware: SUNW,Sun-Fire-T200

Any details on which specific version of CVS I should get, the setups (env variables) I need to setup, any ports I need to setup, would be much appreciated. (Or even links to documentations).

 

I did try to use Google, but seems like my Google skills have lost its touch.

See if this helps:
http://forums.xisto.com/no_longer_exists/
Also related:
http://forums.xisto.com/no_longer_exists/

Edited January 26, 2008 by dserban (see edit history)

I have the impression, from what you posted, that you may be flexible about the type of repository you are going to install. If you are cloning a CVS repository from someone else, disregard this comment.

 

I have used CVS, SVN, RCS, and some really dark-ages revision control systems on mainframes. In my opinion, SVN is the best. It's also the newest, and was developed specifically because the developers of CVS refused to remove some of the warts on their software design.

 

A comparison of CVS and SVN is here. As you can see at the bottom, the author considers their advantages and disadvantages almost equal. The website for Subversion (SVN) is here.

 

For me, the most compelling advantages of SVN are:

Directories, renames, and file meta-data are versioned.

Commits are truly atomic.

The meaning of these terms is explained on the SVN website. The effect is that most of the things a "reasonable person" would want to do are nearly automatic in SVN.

 

P.S.: The SVN download page reports that:

Binary builds of Subversion for SPARC/Solaris 2.5 – 10 and x86/Solaris 8 – 10 are available at: http://www.sunfreeware.com/introduction.html .

Maintainer: CollabNet, Inc.

CollabNet Subversion is Subversion compiled and tested by CollabNet, and deployed with CollabNet's recommended configuration for the enterprise.

Edited January 28, 2008 by docduke (see edit history)

Just about the googling thing : what about trying that way ?
https://www.google.fr/search?hl=fr&q=hoB+sun&meta=
Gives nice replies like this

Setting Up a Local CVS Repository - Sun Java Studio Creator 2 ...- [ Traduire cette page ]Setting Up a Local CVS Repository - Sun Java Studio Creator 2 Update 1 - Online Help. ... To set up a local CVS repository, you must have a CVS command-line ...developers.sun.com/docs/jscreator/help/2update1/vcs-nb/vcs_create_local.html - 7k -

or like this :

HOWTO - Use CVS- To set up a CVS repository, you must define the environment variable ... to initialize and set-up the CVS repository. This only needs to be done once. ...owen.sj.ca.us/~rk/howto/cvs.html

Seems rather promissing. I will not go further (I'm an AIX guy, not a Sun one, but Unix is still worldwide...)

See if this helps:

http://forums.xisto.com/no_longer_exists/

Also related:

http://forums.xisto.com/no_longer_exists/

Thanks dserban! The first link did not hit on the target, but I guess, its TOC (http://forums.xisto.com/no_longer_exists/) should serve my purposes.

 

The second link is also a gold mine. It will help me setup the process guidelines in the organization.

 

I have the impression, from what you posted, that you may be flexible about the type of repository you are going to install. If you are cloning a CVS repository from someone else, disregard this comment.

 

I have used CVS, SVN, RCS, and some really dark-ages revision control systems on mainframes. In my opinion, SVN is the best. It's also the newest, and was developed specifically because the developers of CVS refused to remove some of the warts on their software design.

 

A comparison of CVS and SVN is here. As you can see at the bottom, the author considers their advantages and disadvantages almost equal. The website for Subversion (SVN) is here.

 

For me, the most compelling advantages of SVN are:

Directories, renames, and file meta-data are versioned.

Commits are truly atomic.

The meaning of these terms is explained on the SVN website. The effect is that most of the things a "reasonable person" would want to do are nearly automatic in SVN.

 

P.S.: The SVN download page reports that:

Binary builds of Subversion for SPARC/Solaris 2.5 â 10 and x86/Solaris 8 â 10 are available at: http://www.sunfreeware.com/introduction.html .

Maintainer: CollabNet, Inc.

CollabNet Subversion is Subversion compiled and tested by CollabNet, and deployed with CollabNet's recommended configuration for the enterprise.

Sadly docduke, I cannot easily shift to SVN. Lot of approval and redtape to go through, and if I choose that route, I don't think I can get it done in time.

 

Thanks for those helpful links - will give me some more research material.

 

Just about the googling thing : what about trying that way ?

https://www.google.fr/search?hl=fr&q=hoB+sun&meta=

Gives nice replies like this

Setting Up a Local CVS Repository - Sun Java Studio Creator 2 ...- [ Traduire cette page ]Setting Up a Local CVS Repository - Sun Java Studio Creator 2 Update 1 - Online Help. ... To set up a local CVS repository, you must have a CVS command-line ...

developers.sun.com/docs/jscreator/help/2update1/vcs-nb/vcs_create_local.html - 7k -

or like this :

HOWTO - Use CVS- To set up a CVS repository, you must define the environment variable ... to initialize and set-up the CVS repository. This only needs to be done once. ...

owen.sj.ca.us/~rk/howto/cvs.html

Seems rather promissing. I will not go further (I'm an AIX guy, not a Sun one, but Unix is still worldwide...)

The first one is on installing a local repository.

 

Second one - http://owen.sj.ca.us/~rk/howto/cvs.html - bingo! Thanks. I seriously must have had a vodoo on my Google skills.