use Perl

• Brave Man (Score:1)

  by barbie (2653) <reversethis-{ku. ... m} {ta} {eibrab}> on 2003.04.07 10:44 (#18833) Homepage Journal

  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 :)

  Reply to This

  • Re:Brave Man (Score:2)

    by TeeJay (2309)

    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;
  • Re:Brave Man (Score:1)

    by dws (341)

    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