Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Actually, there is already vc mode support, it probably isn't in the version of emacs you're using though. If you're using a fairely recent GNU emacs you can grab vc-svn.el from the Subversion tarball and you're all set. XEmacs users are out of luck for the time being though.
  • Keep us updated on your thoughts and usage issues. I recently got turned on to the idea of converting to SVN after being exposed to is in the modperl/Apache::Test dev lists.

    I like the web interface a lot better and getting source through a proxy via http:https rulez, but having a copy of Apache2 around just for it seems like a pain, altough I hear CVSWeb groks SVN now too.

    I still can't get my brain to accept how tagging and branching works without a branch/tag command. :-) The other thing that bugs me sti
    • and getting source through a proxy via http:https rulez, but having a copy of Apache2 around just for it seems like a pain

      You don't need to have Apache2 around to use Subversion, just for the webdav stuff (though Apache2 and mod_perl 2 are nearly mature.) You can set up svnserve (ie. svn: urls) which is the most efficient, its analogous to pserver, with less suck and more security. You can also use svn over ssh ( svn+ssh:) like CVS does.

      There's also a few CVSWeb like things out there. WebSVN [schwern.org] is o

      • OK, you've put it another way that makes sense [to me]. I'm installing it now on my dev box. :-) It just so happens I'm working on a new set of modules, so it's a good time to migrate.

        I took a look at your WebSVN. Is it me, or is it slooooooooow?

        Thanks,
        -=Chris
      • This also means that since every file has the same revision you can use $Revision$ as a project-wide $VERSION in all your .pm files.

        I'm presuming that's if you want version numbers of the form 1.49 and so far haven't moved up to 2.0. What do you do if you want to call a release of your module 2.0?

        --
        J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
  • On Windows, the integrated Explorer interface is awesome!

    Screen-shot [darserman.com] The small icons on the files and folders indicate change status.

    One thing that sucks though; once when I renamed a class and had to move a directory with it's contents, that corrupted the SVN database somehow. That was a while ago, so it may be fixed by now. Or it may be the GUI component using SVN the wrong way.
  • Also, jump directly to version 1.1.1 and use the new FSFS repository type. A lot of the problems you might have heard about SVN stem from the old Berkeley DB format.

    I'm not sure who to directly credit for this addition, but I do not that back in the ancient, ancient days of Subversion, before most people even knew it existed, Chip Salzenberg took at look at the project and decreed that it needed to be modified to work with flat files. Unfortunately about that time Eric Raymond showed up and dragged the

    --
    J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers