On Thu, Jan 03, 2008 at 09:01:01AM -0600, George Kraft wrote: > I propose LTP to create usctest-devel-X.Y.i386.rpm and pan-X.Y.i386.rpm > packages with all the headers and libraries necessary to compile and run > a standalone test. Here are the details:
Should we split pan from the tree so it can be its own package? > 1) All the *.o in /usr/local/src/ltp/lib should be put in a library > (libusctest). There already is a libltp.a according to lib/Makefile. > 2) Create a /usr/local/share/pkgconfig/usctest.pc package config file to aid > test compilation. > 3) Put standalone test examples (C, shell, python) in > /usr/share/usctest/examples/. > 3b) These test examples should use automake and follow the GNU Coding > Standard. Personally, I couldn't care less about automake or the GNU Coding Standard. GNU Make is advanced enough these days that you don't need automake to have a good non-recursive build. > 4) Create an ltp-devel.spec file to rpmbuild from the released ltp tar ball. > 5) Create a pan.spec file to rpmbuild from the released ltp tar ball. > > http://www.ibm.com/developerworks/library/l-rpm1/ > > When usctest-devel-1.0.i386.rpm and pan-X.Y.i386.rpm are installed on a > system, then I can write and run ltp fashioned tests with the code that > I'm developing, and not be burdened with entire ltp tarball release. I > just type "make test" in my current working directory. I would like to encourage use of LTP tools as a basis for other test suites. I have yet to see anyone from the community explore the nesting of pan to build interesting workloads. I find that ability invaluable in my testing of cluster products. Nate ------------------------------------------------------------------------- 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/ _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
