of course, people familiar with svn should already know this… lol

but yeah, it can be useful to remove all .svn folders in a flash if you need archive your project for distrobution, and don’t wanna export all the files outta svn,.. also like sxtxixtxcxh mentions, when uploading your web-based apps to the production server…

my approach to it tho would be to create a tag in the repository called production, login then ssh/telnet into the production server, and simply checkout a copy of http://domain/svn/project/tags/production/ for example, into the sites root, or wherever the script lives on the server. then obviously configure apache to block access if any .svn folders are requested. then i’d create a php script which requires me to authenticate, which can execute svn update on the scripts working directory, then i’d just have to copy /trunk to /tags/production and run the php update script (or login via ssh) whenever /trunk is in a production stable form.
thats my web-development and deployment plans, which i’ll be implementing soon together with sxtxixtxcxh on his lib.rario.us project. one of us will blog about the details with working code and configuration options once we’re done