use Perl

• Comments (Score:1)

  by dlc (50)

  Having a full blown Apache 2.0 server seems overkill.

  That's for the server. You only need theAPR libraries for the client.

  --
  (darren)
  • Re:Comments (Score:2)

    by Matts (1087)

    Right, but that probably means it won't ever do disconnected operation. At least not without Apache 2.0 on the client.
    • Re:Comments (Score:1)

      by rooneg (3732)

      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
      • Re:Comments (Score:1)

        by jmason (3282) on 2003.07.11 11:58 (#21992) Homepage

        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, instead of HEAD, but no biggie).
        
        If they differ, mark them as opened for changes 'em with "p4 edit". This will *not* check the latest code from the repo; instead it just marks the *current* file contents as changed and possibly requiring checkin.
        
        Finally, "p4 sync; p4 submit". Any changes are checked in; any marked-for-edit files that haven't really changed, will be skipped since there's no delta; any conflicts have to be dealt with using "p4 merge". Super-easy!
        
        for deleting files, renames, etc., things get a little trickier, but those are infrequent occurences. The above served me very well for a long time using p4 on dialup, and from the opposite corner of the world.

        Reply to This

        Parent

        • Re:Comments (Score:1)

          by rooneg (3732)

          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,
          • Re:Comments (Score:2)

            by Matts (1087)

            Checking things in is the entire point for me.