Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to email@example.com.
"Tony Hoyle" <tmh at nothing-on.tv> schrieb im Newsbeitrag news:3D6BDDB3.70309 at nothing-on.tv... > > I have installed the scripts (cvslog, cvsprep) in the CVSROOT > > directory of repository, which didn't cause any problems. > > But every time something is committed into the repositories > > CVSROOT the execution permissions are removed by cvsnt. > > Is this expected? Or is there a configuration parameter to > > avoid this. > > There was perserve permissions on CVS once - most of the code is still > there (commented out) in the source. That is what I remembered too. > It was disabled in Unix CVS ages ago because it is apparently dangerous. Just being curious, why is this dangerous? > I'm looking at rewriting something for cvsnt to do basic permission > preservation (difficult because the old code was extremely unix specific > and I can't use much of it). OK. As you may have read, I changed my commitinfo and loginfo files pointing to an executable outside CVSROOT rather than the scripts itself. This executable, e.g. a shell or perl, calls the scripts I want to execute. This works perfect for me. -- Gerhard Stegemann