All the Perl that's Practical to Extract and Report

Navigation

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

Actually, you don't even need Apache on the server either if you don't want to. You can run our custom tcp protocol tunneled over ssh (like many people do with cvs today), if you prefer to avoid apache.
As far as disconnected operation, that's a question for another day. People have talked about possibilities for it, but it's strictly a post 1.0 issue at this point.
I suspect it will be something along the lines of each user having a separate local repository, and supporting merging of changes between r

btw I think svn is pretty similar to p4 in its support for disconnected operation; it's pretty trivial to hack. Here's how I did it when I was using p4:

When you disconnect, you stop using "p4 edit" and start using a homebrew script like "o4 edit" instead, which just chmods the files +w.

When you reconnect, use a script which runs "p4 diff" to compare your entire checked-out tree with the checked-in versions of those files. (Optionally, it can compare them with the revision they were checked out from, ins

actually, svn's support for disconnected operations is much cooler than the work arounds you can come up with for p4;-)
we keep pristine copies of all files you've checked out, so you can run add, remove, diff, status, and a number of other commands without ever having to touch the network. this also let's us send diffs to the server instead of the entire file as CVS does when you commit.
so in short, you can currently do just about anything other than finding old versions of files, reading log entries,

perforce rocks. It's got a great web GUI, and it can do the best automated merges of any SCM tool I've used. Most importantly, it's really well supported, great company, open mailing lists, etc.
Arch -- sounds good -- like p4 it does good automated merges. However I've heard negative things about the maintainer's attitude etc. This is a thumbs-down for me.
svn -- good in all respects except for automated merges.
Nowadays, I'd use p4 for a commercial project or svn for a free one.

To me, the big plus of p4 compared to svn is this ability to merge with history. But for other aspects, I find svn easier to use. No need to 'p4 edit' files, supports several operations (svn diff, svn status) without a connection, customizable. Note that I don't use GUIs.

You could use p4 for free projects, for personal repositories. I think that several former pumpkings do.

oh yeah -- BTW if Clearcase comes up, run away screaming.
Here's my thoughts on that "product" [xent.com]. Summary: right up there with most of the other Rational products in terms of usefulness, reliability and usability;)

You know, Schwern has some good things to say about Aegis. While he certainly realizes that it's not necessarily the best solution, it's a very nice one. If Aegis was more user-friendly (i.e., idiot proof for the non-technical folks and available on NT without Cygwin), I think I would probably dig into it more.

: 1. What is the possibility of this being added in the future?
In the near future, the probability is close to zero. In the distant
future, I'll be dead, and posterity can do whatever they like... :-) --lwall

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.