[Zope-Checkins] SVN: Zope/trunk/ - Applied patch for

Tim Peters tim.peters at gmail.com
Fri Mar 18 17:30:10 EST 2005

[Martijn Faassen]
> Would it make sense to use svn:externals, and then add a read-only
> link to ZODB using a svn:// url to some tag or branch instead?

I don't know.  People have talked about it, but nobody has tried it. 
It seems likely that would create new problems too; the SVN manual
names some of them.  I don't see anything there about a "read-only"
option for externals, BTW.

> Then this kind of mistake typically wouldn't happen, as you'd only have a
> writeable checkout if you checked out ZODB explicitly.
> I understood from Jim the 'stitching in by copying' process was to support
> doing local changes,

That may have been his intent.  Or it may have been to isolate Zope
from concurrent changes in ZODB, ZConfig, zdaemon .... Mabye both. 
Making local changes to external projects doesn't really make sense to
me, unless the idea is that the host project is effectively forking
the external project (doesn't want to track changes to it anymore). 
It could make more sense if someone in Zope-land took responsibility
for stitching in new copies of ZODB, ZConfig, zdaemon, ..., but so far
nobody has.

> but now you seem to want to avoid them, so it gets somewhat confusing.

Hey, I'm consistent:  I complained about this arrangement starting the
hour it was announced <wink>.

We can't have it both ways here:  if the intent is to make a change to
ZODB, then the change must be made _in_ ZODB.  If the intent is that
Zope wants to fork ZODB, then checking in changes from Zope's copy of
ZODB is appropriate (but then the person doing that fork is
responsible for maintaining the fork too).  Unfortunately, the SVN
setup favors the forking model, which doesn't actually appear to be
what anyone wants.

More information about the Zope-Checkins mailing list