-----BEGIN PGP SIGNED MESSAGE-----
Jens Vagelpohl wrote:
> On 17 Jul 2005, at 20:31, Chris Withers wrote:
>> Jens Vagelpohl wrote:
>>> - "Close off" or "freeze" the CMF projects on cvs.zope.org to
>>> either disallow checkins or bring up big fat warnings if someone
>>> tries to. Input and ideas on this are welcome, if it was up to me I
>>> would use the "commitinfo" file in the CVSROOT to completely
>>> prevent updates as the first step.
>> I like the way this was done with Zope's CVS: the HEAD was cvs
>> delete'ed and files cvs add'ed saying where to go look for the new
> Right. (Here comes out my CVS ignorance:) Does CVS recursively delete
> whole projects or does this require some script that deletes folder
> contents before the folder can be removed? I dimly remember having
> tried to cvs remove folders at some point and it wouldn't let me.
You can't remove directories in CVS through its normal interface (and
shouldn't "back-door" it); instead, you end up doing something like:
$ find . -type "f" | grep -v CVS | xargs cvs rm -f
to remove all files. I did that on the CVS head when the main Zope
repository moved over.
> This would have to happen in conjunction with my earlier suggestion
> about using commitinfo since unlike the Zope repo we really want to
> completely prevent checkins.
If we did that on the trunk and each of the active branches in CVS, we
would be safe, without having to hack commitinfo.
Tres Seaver +1 202-558-7113 [EMAIL PROTECTED]
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Zope-CMF maillist - Zope-CMF@lists.zope.org
See http://collector.zope.org/CMF for bug reports and feature requests