On 4 August 2011 01:59, David Weintraub <qazw...@gmail.com> wrote: > ... > SNIP > ... > I have what I call my Kitchen Sink pre-commit trigger that does all > sorts of stuff. One of the tasks it can do is "ban" files based upon > their name (either regular expression or Ant glob). If a user adds a > file with a forbidden name, the commit is rejected and the user is > informed of the offending file. The user has to remove the file from > their commit and try again.
Thanks guys. I'm just stupid. I've been going on and on about what we want to do, but I haven't even stated the obvious: * It's just about removing stale files from being tracked by Subversion, _without_ committer intervention. Basically, our developers (did|can do) this thing manually (remove an older version of a binary they are committing). I wanted to automate this. That's all! So, after the discussion here, it's evident I'm doing this all wrong. I've now just reverted our stuff to the last best working state, and I'll be working on something based on: pre-commit (as much filtering as possible during this stage) post-commit (update the checkout) rsync (mirror the checkout for publishing; do not reflect stale files) cron (to svn rm; svn ci the stale files) -- GPG/PGP ID: 19BAA7AD
