I think it is ahead because it was the first of the new VCS systems. The only 3 that really matter now (IMHO) are svn, git, and bzr. As svn was the first out there in the wild that actually worked, and made a huge difference against the older VCS's (SCCS, RCS, CVS), the switch was obvious.
Reasons for choosing either of the three may be well beyond the system itself. I chose git for a few not so obvious reasons:
- Subversion has way too many dependencies, and I didn't get it to work on HP-UX in 64bit mode in 5 working days, after which I gave up. (I was able to compile git to something that partly worked in about 4 hours).
- bzr is based on python, and I don't have python on HP-UX, and also don't want to enter the vortex of yak-shaving into getting that to run on HP-UX and maintain it in the future (in 64bit mode, as our main target for a new VCS was 64bit-only HP-UX). The base packages might be available from different sources, but they are all 32bit and won't cooperate in that 64bit environment.
- The future of perl5's VCS is git. We'll move from perforce to git after the release of perl-5.8.9, so knowing that VCS beforehand was a pre.
Enjoy, Have FUN! H.Merijn
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|