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

[Jim Fulton]

Tim Peters wrote:
> [Tres Seaver]
> 
>>...
>>+1 for converting any CVS-induced '$Id$' expansions back to '$Id$' in
>>the repository;
> 
> 
> It won't be enough, because of CVS-specific code like
> 
> __version__='$Revision: 1.22 $'[11:-2]
> 
> in various places.  When "the poor dumb schmuck who has to log in to a box
> and try to diagnose why the system deployed last year is broken", exactly
> what are they relying on?  If it's "creative" use of CVS gimmicks (like the
> __version__ defn above), mechanical $Id$ restoration isn't going to help.

The __version__ code should go.  Nothing uses this anyway.

$Id$s aren't subject to this.

> 
>>could we do this in a commit hook, if svn doesn't do
>>it by default?
> 
> 
> A one-shot script would probably work better, if this is to be done.

I think a one-shot edit to get rid of __version__ assignment is warrented.

If your theory that svn diffint/merging is clever enough to do the right thing,
then I'd prefer to keep the $Id$s and set the relevent property.
Then we'd set the relevent svn proprty as a simple script.


Jim

-- 
Jim Fulton           mailto:jim at zope.com       Python Powered!
CTO                  (540) 361-1714            http://www.python.org
Zope Corporation     http://www.zope.com       http://www.zope.org