In article <[EMAIL PROTECTED]>, Matthew Persico <[EMAIL PROTECTED]> 
wrote:

> Is there anyone reading who uses CVS to keep track of Perl modules? Any
> special tips or tricks?

> Currently, I've written a Perl script called h2xs_for_cvs that runs h2xs and
> then slaps on CVS headers where appropriate.

> I have a small question. Is there any way to add 'blib' to the list of
> files/directories to be 'cvsignore'd?

besides putting blib in .cvsignore?

> I've created new modules and when I
> try to import them/ commit them, the -I doesn't seem to work. I have to make
> realclean before I import 

don't make anything before the import.  run h2xs, then immediately 'cvs import'
the directory.  when you add new files, just 'cvs add' them.  your h2xs_for_cvs
can also create a standard .cvsignore.

when i have more time, i'll finish extending ExtUtils::ModuleMaker to use templates. :)

-- 
brian d foy <[EMAIL PROTECTED]> - Perl services for hire
The Perl Review - a new magazine devoted to Perl 
<http://www.theperlreview.com>
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

Reply via email to