[Libreoffice] Brittle unit test dependencies

2011-12-19 Thread Stephan Bergmann
http://cgit.freedesktop.org/libreoffice/core/commit/?id=9351f4c1d6a3567c3b013894a0cc08471b4b0156 Tests apparently depend on localedata_en library. is yet another non-obvious dependency the large unit tests in sc, sw etc. have on their environment. I fear that the approach of having such large

Re: [Libreoffice] Brittle unit test dependencies

2011-12-19 Thread Michael Meeks
Hi Stephan, On Mon, 2011-12-19 at 14:10 +0100, Stephan Bergmann wrote: http://cgit.freedesktop.org/libreoffice/core/commit/?id=9351f4c1d6a3567c3b013894a0cc08471b4b0156 Tests apparently depend on localedata_en library. is yet another non-obvious dependency the large unit tests in sc, sw

Re: [Libreoffice] Brittle unit test dependencies

2011-12-19 Thread Stephan Bergmann
On 12/19/2011 03:21 PM, Michael Meeks wrote: Well; hopefully the tinderboxen catch them for us over time - how did you find this one ? But even if we find more and more missing dependencies over time, this does not solve the maintainability problem. No longer necessary dependencies

Re: [Libreoffice] Brittle unit test dependencies

2011-12-19 Thread Bjoern Michaelsen
On Mon, Dec 19, 2011 at 02:21:45PM +, Michael Meeks wrote: My hope of course, is that as we finish gbuild, and move our solver to look ever more like an install set, it'll get easier and less hacky to run these unit tests; eg. with your nice 'services' work, we could even install the

Re: [Libreoffice] Brittle unit test dependencies

2011-12-19 Thread Stephan Bergmann
On 12/19/2011 03:42 PM, Bjoern Michaelsen wrote: On Mon, Dec 19, 2011 at 02:21:45PM +, Michael Meeks wrote: My hope of course, is that as we finish gbuild, and move our solver to look ever more like an install set, it'll get easier and less hacky to run these unit tests; eg. with

Re: [Libreoffice] Brittle unit test dependencies

2011-12-19 Thread Bjoern Michaelsen
On Mon, Dec 19, 2011 at 04:13:10PM +0100, Stephan Bergmann wrote: Just to be clear: This is unrelated to and does not solve the problem of those non-obvious runtime dependencies. Well, if the installation is in gbuild completely, you could depend on everything in the installation dir from a