tseaver at zope
Mar 22, 2005, 7:02 AM
Post #1 of 1
-----BEGIN PGP SIGNED MESSAGE-----
Re: [Zope-Checkins] Re: SVN: Zope/trunk/ - Applied patch for
Martijn Faassen wrote:
| Tim Peters wrote:
|> 2. If, perhaps in frustration due to noticing that #1 had no
|> effect, they cd to the root of the working copy of an external, and
|> svn commit from there, the changes *will* commit, and will actually
|> change what's checked in on the external's release tag. Everyone
|> else will "see" the changes then, but the external's release tag
|> will no longer contain what was actually released.
|> If so, "checking in from a wrong project" plain sucks, externals or
|> not. If it were possible to mark externals as "read only", that could
|> help. Ditto if it were possible to mark a stitched-in copy as
|> read-only. Don't know whether either is possible.
| It's possible to mark them read only, sort of. In fact you have to, to
| make read-only Zope checkouts work. It's just a matter of using the
| read-only (for svn.zope.org at least) svn URL instead of svn+ssh in the
| externals definition.
| It'd be nicer if svn had some way to *really* say read-only, but this
| does work in practice. :)
The SVN refuse to recognize the lack of "read-only copies" as a defect,
but there is a workaround, which is to add rules preventing checkins to
portions of the tree:
We could adopt such rules for the 'tags' section of the repository
(perhaps granting "fixup" rights to a restricted set of user IDs).
One would then be able to define the 'svn:external' property pointing to
the "read-only" tag with reasonable safety.
Tres Seaver tseaver [at] zope
Zope Corporation "Zope Dealers" http://www.zope.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Zope-Coders mailing list
Zope-Coders [at] zope