1 |
Hi, |
2 |
|
3 |
Ciaran McCreesh <ciaran.mccreesh@××××××××××.com>: |
4 |
|
5 |
> On Mon, 9 Mar 2009 23:20:03 +0100 |
6 |
> Christian Faulhammer <fauli@g.o> wrote: |
7 |
> > Package A goes stable, test suite passes. Package B (a dependency |
8 |
> > of A) goes stable in a newer version, which will cause A to not |
9 |
> > merge in stable profile. This happens all the time and is no |
10 |
> > special case. |
11 |
> |
12 |
> Uh, you *are* testing things that use a library before you stable that |
13 |
> library, right? |
14 |
|
15 |
When I was an architecture developer I tried to. But when stabilising |
16 |
a minor version of curl (for example), testing all reverse dependencies |
17 |
is no option. But this broke tests for Bazaar for example in stable. |
18 |
Or another issue. Badly written Autoconf systems which will break in |
19 |
src_test() with a different version of intltool, which is not a direct |
20 |
dependency. That pitfall hit me several times in the last years. |
21 |
The more, x86 e.g. ranges from embedded Geode platforms to dual core |
22 |
desktop systems and running the sqlite test suite on the first is no |
23 |
fun. As a user I would not accept two hours of build time. |
24 |
Test-driven development is great, but not so widely used as one could |
25 |
wish it to be. |
26 |
|
27 |
> Besides, if a newer version of a library breaks a package using it, |
28 |
> you most definitely want to know about it before you end up merging |
29 |
> something that won't work. If src_test is failing where it used to |
30 |
> work, it's a very good sign that something's broken, and you shouldn't |
31 |
> be carrying on. |
32 |
|
33 |
Arch devs run test suites and won't stabilise if it fails (except some |
34 |
special cases). |
35 |
|
36 |
V-Li |
37 |
|
38 |
-- |
39 |
Christian Faulhammer, Gentoo Lisp project |
40 |
<URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode |
41 |
|
42 |
<URL:http://www.faulhammer.org/> |