Hi folks,
I'm asking that anyone who is interested in helping out LTP please
contribute by testing with the testscripts/build scripts on a
semi-regular basis:
.../testscripts/build/test_install_in_build_tree.sh
.../testscripts/build/test_install_out_of_build_tree.sh
.../testscripts/build/test_out_of_build_tree.sh
I've added these scripts for three identified common fetch ->
build -> test scenarios:
1. Install in source tree.
2. Install out of build tree, but build in source tree.
3. Install out of build tree, build in source tree.
They all assume that the end-user has access to CVS today, but
that can be tailored to meet other needs [in the future].
What I'm requesting:
1. I would appreciate the feedback.
2. In order to ensure build integrity and compatibility obtaining
a profile of common distro configurations (kernel configs, build
tools, etc) so I can better tailor the tests to find known build and
configuration issues before other folks do by accident would be
helpful. If I could obtain access to distro ISOs that aren't mirrored
anymore (with binary packages to install the tools from), that would
make my life a lot easier.
Please CC me the results so I can analyze this and improve the
overall end-to-end process.
Thanks,
-Garrett
------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list
