While doing some further tests on windows I began to realize that there is
no reason why the regression scripts should use the source for any kind of
testing. The code is compiled on a completely different platform and copying
the entire source tree to a different machine/vmware seems like more work
than it should be. Perhaps the win32 regression scripts could be configured
to use the nsis installer to setup the regressions instead of actually
copying the binary files from bacula/src/win32/installer/release. This way
doing regression testing would be as easy as copying winbacula-*.exe to a
directory and running a batch script.
The only issue with using the installer is that the installer cannot install
everything without user intervention. Perhaps the installer could be
configured to accept user-arguments which specify the different install
modes and options. This would solve a number of problems for Win32
regressions and also include testing the installer as part of the regression
tests.
Let me know if I am not being reasonable with this :P
Sincerely,
-Michael
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-devel
