Quote:
Originally Posted by prickle
well, it IS possible to write a script that will find the files you want even if they've been moved to a new directory, but that's besides the point 
Also, running scripts that you don't understand is generally a bad idea for any operating system, not just Linux... e.g. the virus cesspool that is Windows and more recently Mac OSX can no longer claim to be "virus and malware free" thanks to a wide spread botnet infection last year.
but i guess that's a bit off topic.
I did write my own build script (in Perl w/ a child bash script) that would do the whole shabang sometime ago. It started with an SVN compare between local and source, then if there were updates, it would svn up, and copy to a build dir, tweak the makefiles to my specification, compile, stop backup and replace the existing server. I haven't used it in a while due to complications with Perl, and now the change to CMake.
If I find some time in the coming weeks, maybe I'll tweak it and share it. |
true enough on all points. the problem lies with the assumptions made by the end user (and the script, in this particular case), which was what i was getting at. it's always best to know what is going on when you are running or installing something on your machine, regardless of the operating system. i just cringe out of habit when it comes to admins running things unaware on linux. it's really not worth the air it takes to expel a sigh when it comes to windows.
Threaded Mode
