Re: CVS for Cfengine (Was: Re: Bugzille for cfengine)

[Matt Small]

I've had to deal and administer a few repositories, including CVS and
Subversion (as well as some horrible, horrible commercial alternatives).

Generally, I'd recommend CVS for any project looking to start with a source
repository, for 2 main reasons:

 - it's brain-dead simple; easy to use, easy to administrate, easy to recover
        from errors, and many (most?) developers are familiar with it
 - it's easy to upgrade to anything else; every other tool (including svn) has
        a tool to import a CVS repository

If you find that you need more than CVS, then you can start looking into other
alternatives when that happens, and you have a clean upgrade path.  And, by
that point, you'll know what problem you're trying to solve, so you can choose
between Subversion, Arch, or whatever else might fit your needs.

-matt

> 
> So ...Sven says:
> 
>  % So PLEASE: Wherever you create a repository for cfengine, please create 
>  % a subversion repository rather than a CVS repository.
> 
> 
> There are a lot of issues:
> 
>       1) What does Sourceforge support
>       2) What features does SVN have instead of CVS
>       3) what skills do the potential developers have
>       4) Who is going to be doing the commiting
>       5) are there any CVS to SVN conversion tools
> 
>       CVS is the default because 
>       a) it is known
>       b) It is available
>       c) it has the widest penetration
>       d) It does the basics that are needed.
> 
>       However, I am certainly open to coming to agreement on
>       something else. 
> 
> At the moment, there is no source control process. So it will
> be possible to start with any one that we would like. 
> 
> What is important to me is to gain a consesus from the core uses of
> cfengine. I know that each of us have tools that we like and that
> this can be important to us. But it does not matter if in the end
> we chase off other folks who would have created great things. 
> 
> So while I hear sven's words and can feel his angst, I am 
> very interested in understanding from the cfengine community what
> tools they need for a successful system for the group.
> 
> So I would like to hear from everyone:
> 
>      a) How likely are you to submit code?
>      b) How likely are you to use the cvs/rcs/svn/bitkeeper/??? archive?
>      c) What is your first choice tool for source control?
>      d) What is your sencond choice for a tool?
>      e) What is the most important issue around source control?
> 
> 
> 
> Here are some subversion links that are worth considering in the 
> conversation. 
> 
> 
> http://www.red-bean.com/sussman/svn-anti-fud.html
> http://svn.haxx.se/users/archive-2003-12/0730.shtml
> http://sial.org/howto/subversion/cvs-migrate/
> http://subversion.tigris.org/project_faq.html
> 
> 
> 
> 
> -----
> John Sechrest          .         Helping people use
>                         .           computers and the Internet
>                           .            more effectively
>                              .                      
>                                  .       Internet: address@hidden
>                                       .   
>                                               . http://www.peak.org/~sechrest
> 
> 
> _______________________________________________
> Bug-cfengine mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/bug-cfengine
>