Hi, guenter geiger hat gesagt: // guenter geiger wrote:
CVS provides 'commitinfo' for this very purpose, combined with this perl script 'cvs_acls' (http://collaboratory.psc.edu/tools/cvs/faq.html) Plus 'commitinfo' can also be used for running pre-checkin test routines. Here's what the docs have to say: http://www.cvshome.org/docs/manual/cvs_18.html#SEC167
I'll take a shot at setting this up if someone is interested.
Yes, if someone wants this you just have to set it up. I am not at all against it, I just did not do it because it is not relevant for me personally.
I think, in general this is a good idea. Developers like Yves and Thomas, who are concerned, that their code might be changed without their approval, need to have a way to make sure, that this doesn't happen.
Personally I welcome bugfixes for my externals (and makefiles :), so I don't care, if I'm the only one or not with write permissions to ext./footils/. I trust you guys :) ... but it's not only a matter of trust, it also is a matter of security.
I also think, that the Pd main directory "pure-data" should have a stricter checking of permissions. I would appreciate it, if Miller would use sourceforge for his releases as well, but I understand, that he as the main developer needs to have a branch/directory, where only he and maybe a handful of intimates can commit.
But, I already consider the external CVS as a success, and it makes life a lot easier for me already, hopefully, in the near future it will make the live easier for all pd users too.
I has made life easier for me, too, and I really think, that the CVS is one of the great things, that have happend to the Pd community recently (the other is "undo"). Having all externals alway at one's "cvs update"-fingertips is so much more comfortable than surfing the web for externals...
ciao
Frank Barknecht _ ______footils.org__