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 sales@march-hare.com.
> perltidy and it helps to format the > commited Perl sources in a suitable way) There are many good reasons NOT to do this. It is generally "better" to run perltidy and check for differences between the "tidy" version and the "checked in" version - if they are not the same then the developer is attempting to checkin an "untidy" version and the commit should abort with a message like "go read the standards and guidelines before attempting to commit code". Some of the most popular reasons for NOT automatically tidying are: * developers do not unit test the "actual" code * such scripts can damage the "intent" of the programmer Another alternative is to have a "reviewed" branch which code gets sent to once a code review takes place - and that is "tidy" - not the trunk. > Now the question: How can I make cvsnt > to update automatically the sandbox after There is no such thing implemented because the above techniques are the primary ones used. If you really really want to work this other way that you documented then you will need to write your own shell script called cvs, and rename cvs to cvsnt and then when the user enters a cvs command you can run "cvs commit" then "cvs update". Regards, Arthur