Quote:
Originally Posted by c0ncrete
this is one of the reasons why using an automated installer script ends up being more of a hindrance than a help.
if you'd have been reading a guide that told you copy the conf files from the old directory, you would have noticed they were no longer there. the script isn't sentient and is unable to tell you that something was missing because of how it was written.
running scripts on linux that you can't read and understand what they do is generally a very very bad idea.
|
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.
Threaded Mode
