On Wednesday, October 02, 2013 03:55:49 PM Joe MacDonald wrote: > Hi all,
Hello. > The first of these is just a minor tweak that makes it possible for me to > use the existing INSTALL_BIN_MACRO when installing the other components in > the tools/ directory. Okay, I'll take a look; that sounds reasonable to me. > I broke the python changes out into a separate commit because I'm not sure > it's the right thing to do at all and I'm not sure I did it in a sensible > way. > > The middle one is the one I care about (and have tried in my own scenario), > though. It is convenient to have the regression tests able to run on a > system that isn't the one I built libseccomp on originally. Any interest > in this? The tests are there to help us, the libseccomp devs, and perhaps the packagers, catch problems in the development and packaging stages, it isn't something a user, or even an application developer, would ever find useful. For this reason I don't want to install the tests. However, as usual, I'll keep an open mind on the issue. If you can convince me that the advantages outweigh the disadvantages we can revisit the idea. -Paul -- paul moore security and virtualization @ redhat ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk _______________________________________________ libseccomp-discuss mailing list libseccomp-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libseccomp-discuss
