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.

Moving from CVS to Subversion 4 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • The Good News:

    It's SO much easier to work with at a tool and people level.

    Everything has a URI! I've ever been releasing to CPAN by giving PAUSE an upload URI and having it pull the file straight out of the repository. Release tarballs all have URIs.

    You can checkout anon, and then it will automatically change to a user/pass account if needed when checking in. And so on, and so forth.

    The Bad News:

    There are no tags. No really. Tags are implemented by making a complete copy of your project into another directo
    • I wouldn't worry too much about tags and branches. It's mostly just a question of getting used to how subversion does things... For instance, checking out the root of the project is not generally required. It's much easier to just check out the trunk or branch that you're actually concerned with.

      As to converting tags into branches, yes, this can be done easily by accident. I wrote a subversion hook script to prevent this -- it stops commits going ahead if you're committing to a tag. Shout if you wan

  • You say "of course" about moving to svk, but I'd hold back. It's not necessarily a good thing. Unless you specifically need to be able to work without access to your repository, it's not worth doing. I only have svk on my laptop, and only for airplane trips.
    --

    --
    xoa

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