I would suggest two things:
1) I still think it MORE important for the builders of source packages
to do this than for the end users. Else what value are the source
package builders really providing?
2) If it is important for end users to run such tests (to test
correctness of configuration) then the error messages should point to
problems in the configuration, rather than the developer-centric
messages that are emitted now.
I think you've just become accustomed to the use of testsuite that is
suboptimal because there is nothing better.
> -------- Original Message --------
> Subject: Re: Victory - built subversion from RH9 source rpm!
> From: "Jani Averbach" <jaa@jaa.iki.fi>
> Date: Fri, February 11, 2005 2:54 pm
> To: scohen@javactivity.org
> Cc: "Kenneth Porter" <shiva@sewingwitch.com>,
> users@subversion.tigris.org
>
> On 2005-02-11 14:42-0700, scohen@javactivity.org wrote:
> > The larger issue, which no one wants to discuss, in spite of my several
> > attempts to raise it, is whether the developer unit-test suite is an
> > appropriate test suite for inclusion by default in source-build
> > packages.
> >
> Let's talk about it. =)
>
> I think it is very reasonable thing to do for __source_build__
> packages. We have seen several post on dev@ and users@ when something
> has went wrong with build or link, and exploded right away with test
> suite.
>
> I have even planned time to time make the test suite a stand-alone
> system (which it is quite much, btw), so that you could stress test
> your binary installation or current setup with it.
>
> Of cource this is just IMHO.
>
> BR, Jani
>
> --
> Jani Averbach
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 11 23:13:52 2005