I just subscribed to the list :) In case you still need it, here is the patch I sent before with my note. Again, Thanks for your support.
--- snip ---
We are using your Unattended scripts to create a new standard load for our company. This has been really, really helpful. Thanks a lot !
I am attaching the following patch for z:\dosbin\install.pl to allow users specify custom build scripts. This allows users to define the script filenames in the file z:\site\bscripts.ini. If the file does not exists, your defaults are used: base.bat, developer.bat... etc. Hope you find it useful.
*
*From: Patrick J. LoPresti <[EMAIL PROTECTED]>
* Re: re: startup scripts base/developer et all* <http://sourceforge.net/mailarchive/message.php?msg_id=6057747> 2003-09-15 13:04
I think this is a good idea. (Actually, I think somebody sent patches once, but I seem to have lost them...)
--- install.pl.old Fri Jul 18 19:25:54 2003
+++ install.pl Fri Jul 18 19:15:13 2003
@@ -506,9 +506,21 @@
set_value ('_meta', 'top',
sub {
- print "Choose post-installation script to run:\n";
my @scripts = ('base.bat', 'sales.bat', 'developer.bat',
'build-server.bat', 'training.bat');
+ my $buildscripts = "z:\\site\\bscripts.ini";
+
+ if (!open BUILDSCRIPT, "<$buildscripts") {
+ printf "No Custom Build Scripts Defined. Using Defaults...\n";
+ }
+ else {
+ printf "Using Custom Build Scripts from $buildscripts\n";
+ my @tscripts = <BUILDSCRIPT>;
+ @scripts = split /[ \t\n]+/, join (" ", @tscripts) ;
+ close BUILDSCRIPT
+ }
+
+ print "Choose post-installation script to run:\n";
my @choices = map { my $full = "Z:\\scripts\\$_";
($full => $full);
} @scripts;
