Isolating qa data?

["Dr. David Alan Gilbert" <dave@xxxxxxxxxxx>]

Hi,
  Given the xz hack, would it make sense to isolate the qa data files
under a single directory, e.g. qa/data/vcl/cppunit/pdfexport rather
than vcl/qa/cppunit/pdfexport ?

  What I'm thinking is that a cautious packager could set it up so
that during the build qa/data wasn't readable, then having built and
copied their installation out, then they could perform a make check
having reenabled access to qa/data/

 To be clear I'm not worrying particularly about LO,
but fundamentally a lot of the test files start off as random bug reports
and it's rare to look inside the test files for anything odd.

 Just an idea,

Dave
-- 
 -----Open up your eyes, open up your mind, open up your code -------   
/ Dr. David Alan Gilbert    |       Running GNU/Linux       | Happy  \ 
\        dave @ treblig.org |                               | In Hex /
 \ _________________________|_____ http://www.treblig.org   |_______/