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.
  • I, for one, would be more than happy to see Applying RCS and SCCS (ORA) revised and updated to include CVS (and get rid of SCCS), plus whatever else.
  • I'd be more than happy to help you with the book. I've been put in charge of CVS in my camp and we also run Bugzilla, Viewcvs, WinCVS, etc. I also want to get an interal IRC server and intergrate a CVS/Bugzilla bot that interacts with both. :)
    --

    -biz-

  • On a side note I am thinking of writing a book for people who end up running version control systems. Something like 'Practical Version Control' covering CVS, SVN, RCS and some of the GUI's and plugins available as well as handy recipes and scripts (like blogging commits, integrating bugzilla, web interfaces, etc)

    This is a fabulous idea. I've wanted to see a Practical $foo series for a while, and version control systems are definitely a good one to include.

    +1

    --
    (darren)
  • While a thoroughly good idea, the time taken to research all varieties of Version Control, is likely to be a long time. How detailed do you go and what apps do you do you cover? Some are limited to specific platforms, others are limited by their accessibity (command line verses GUI). If you do manage it, much respect will be due.

    I was introduced to version control some 15+ years ago, with SCCS and RCS. Scary then and scary still. Thank $deity for CVS :)

    • I did a dissertation on version control as part of my final year project (I also designed and implemented a http-like server that provided abstract info on RCS and ither VCS directories on the server with a GTK client).

      My plan is to cover RCS, which would also give a good introduction to Version Control basics. Then cover CVS and SVN.

      The core of the book would be practical applications of version control

      • the how and why of branching and merging and tagging.
      • perl and shell scripts and recipes for logi
      --

      @JAPH = qw(Hacker Perl Another Just);
      print reverse @JAPH;
    • While a thoroughly good idea, the time taken to research all varieties of Version Control, is likely to be a long time.

      Berczuk and Appleton do a high-level skim of the common version control packages in Software Configuration Management Patterns [amazon.com], though they focus on laying out a common language for talking about SCM, and on high-level patterns of usage, and don't get down to the level of actually giving concrete example of how to use product X. Still, if you're going to write a book on CVS, it might hel