Mercurial change from Large CVS repository + Large Binary Libraries

Francisco Diaz Trepat - gmail francisco.diaztrepat at gmail.com
Mon Feb 18 08:41:10 CST 2008


Hi all,

Although I am newbie (although I been reading some about mercurial from the
video conference in google) I would like to start to propose here at work to
switch to Mercurial.

I think we make an excellent case for it. And my intention is also similar
in part with Tom's mail of gigantic repositories, and that is to get your
thought's out to see if we can enrich our current process of scm.

Some characteristics:

   1. We work from far apart countries, europe and south america.
   2. We currently use CVS.
   3. We have a large repository with many years of history, many
   branches, many merges, many of everything.
   4. We have C++ server and Java Client. We have libraries on two
   hardcoded (ugly) paths S:\libraries and S:\tools, and we have a lot of
   libraries. A lot. This part I am told is almost unfixable due to large
   quantities of files having the "s:\libraries\lib.dll" path on them.
   5. Libraries are not in the CVS which server is in europe so we don't
   want to have a traffic JAM.


Goals:

the main goal of which mercurial would be part of the solution proposal
together with maven (maybe) is:

   1. open console
   2. checkout
   3. build
   4. everyone is happy

Apart from point 4 (which could be accomplished by some prozac :-)... )

One of the goals is to be able to checkout a revision with its libraries,
instead of having them only in the filesystem.

Can you guys share some
comments/thoughts/ideas/links/dontbodermemessages/etc on:


   1. Large CVS repositories being
Converted<http://www.selenic.com/mercurial/wiki/index.cgi/ConvertExtension>to
Mercurial.
   2. How can we handle libraries? Should they be in the repository, what
   are your thoughts in general?
   3. In your experience what are the main points to gain from converting
   cvs to mercurial.
   4. Are they any disadvantages as far as you know in converting from
   cvs to mercurial?
   5. And what are the CVS users more prone to dislike an more to like
   about mercurial?. I need good pointer strategies to better convince a very
   reluctant group of developers who only know CVS and will probably be a bit
   deffencive.

Thanks to all,

f(t)

PS: I been reading some post from cvs vs hg kind and have seen the file
version vs repository version discussion, among others.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://selenic.com/pipermail/mercurial/attachments/20080218/b8db7bf4/attachment.htm 


More information about the Mercurial mailing list