chasd wrote: >>> This may be partly my ignorance of svn commands showing, but is >>> there any >>> way to prevent the 'installer' folder from coming back every time >>> you run >>> "svn update"? > >> I'd probably wrap the "problem" into a small bash script and rm -rf >> installer/ when you fetched it. No idea otherwise. > > You can chain the commands using a semi-colon - > > svn update ; rm -rf installer
I may have to do something like that. I already have several other aliases for similar situations, such as updating ports on FreeBSD (csup ports-supfile; cd /usr/ports; make fetchindex). > But then you end up downloading the installer files each time you > update. > A better command would be > > mv ./installer1 ./installer ; svn update ; mv ./installer ./installer1 > > which moves the installer files out of the way during use, but moves > them back so svn only downloads / applies changes. The problem with this approach is that it leaves those files accessible via the web, which is the reason for the warning in the first place. Sure, the path is different but it's just security by obscurity, which is never a good thing on its own. The other suggestion of "chmod 000 installer" is better, but still not as good as never downloading the folder in the first place when updating a current installation. I suppose the folder could be moved to/from a folder that is not web-accessible, but that would only further complicate the situation. Here is another interesting possibility: Could the installer chmod itself 000 after it is finished running? Jim _______________________________________________ List info: http://lists.roundcube.net/dev/
