use Perl

• Too risky? (Score:1)

  by ambs (3914)

  For most cvs modules I have (C with autoconf and automake temporary files, Perl with blib and pm_to_blib files, TeX with temporary files) that line is too risky, unless you create first a .cvsignore file.
  • Re:Too risky? (Score:2)

    by brian_d_foy (44)

    Well, you should look at the cvs status first. I don't do it without knowing what it is going to do first: it just saves me a lot of typing or cutting-and-pasting. :)
    
    And why aren't you using .cvsignore? Hmmmm? Put files like blib and pm_to_blib in the global ignore file!
    • Re:Too risky? (Score:1)

      by ambs (3914)

      Global ignore file? Is there such a thing?
      • Re:Too risky? (Score:2)

        by jonasbn (1153)

        There are plenty of way to define the CVS ignores also globally.
        
        This variable is appended last to the ignore list during a command. The list is built up in this order: CVSROOT/cvsignore, the .cvsignore file in your home directory, the $CVSIGNORE variable, any -I command option, and finally the contents of .cvsignore files in the working copy used as CVS works in each directory. A ! as the ignore specification at any point nullifies the entire ignore list built up to that point.
        
        From: http://cvsbook.red-b [red-bean.com]