[Zope3-checkins] SVN: Zope3/trunk/ Ignore files/directories that are result of a build process, such

[Philipp von Weitershausen]

Fred Drake wrote:
> On Thursday 13 May 2004 01:21 am, Philipp von Weitershausen wrote:
>  > Yup. Btw, the "$Id$" keyword issue has not been fixed yet. We need to
>  > set svn:keywords="Id" on every file where we want the Id keyword to be
>  > expanded. To make svn pick it up, the original string needs to read
>  > "$Id$". A previous CVS expansion of the Id keyword will not get picked
>  > up by svn.
> 
> Perhaps we should examine "the issue" a little more carefully.  Do we *want* 
> $Id$ expansions, or anything else expanded?  I've never seen it as anything 
> but docstring pollution, but I know Jim likes it.

Ok, I'm very indifferent about $Id$ expansion.

> The move to Subversion is an opportunity to revisit this aspect of the 
> guidelines.  Let's try not to encourage this sort of pollution in the new 
> repository.

Sounds like a good idea.

>  > I'm volunteering to do this (by writing a small script that iterates
>  > over files, sets the svn:keywords property and replaces $Id ...$ with
>  > $Id$ accordingly).
> 
> Please, let's not.  Expecting much of end user configurations is a mistake, 
> and it's quite fragile.  It also creates a great deal of burden on developers 
> involved in projects with conflicting guidelines for their Subversion 
> repositories; the closer we can be to living with the default configuration, 
> the better.

Well, it's already sort of too late for that. We already require newly 
added python, zcml and text files to carry svn:eol-style=native.

Philipp