Re: [log4perl-devel] Log4Perl and CVS enhancement

[Lars T. <la...@th...>]

Bobby Nations wrote:
> This is more than a little annoying as we typically will check all
> external source code, such as Log4Perl, into our CVS server for tracking
> and inclusion in our projects.  By default, those two files will get
> hosed up when we check them back out because CVS interprets the
> '\$Log.*\\$" as it's $Log$ keyword.  The only workaround is to tag these
> as binary files in CVS, which works but is a bit of a kludge and it's
> easy to forget.

IMHO it is a very bad policy to allow CVS to do keyword expansion in 
third-party sources. You do not control those sources, so you can never 
be sure that permutations in the source will not fool CVS into believing 
it can safely expand what it thinks are keywords. Your _only_ safe bet 
is to disallow keyword expansion entirely when you check the sources 
into CVS, by using the -ko flag. This is not a kludge - this is the 
exact reason for that particular flag. Write a script to do the 
importing of your third-party sources, if you're worried you'll forget 
the -ko.

> Would you please change the above two files so that they no longer match
> the regular expression, "\$Log.*\\$"?  This would really help out folks
> in the field.  

You are also asking the the authors in all future refrain from using 
anything that CVS (or any other version control system) would confuse 
for a keyword? Not a reasonable request, methinks.

/Lars