1 |
Ciaran McCreesh wrote: |
2 |
> On Wed, 11 Jun 2008 07:53:21 +0200 |
3 |
> Luca Barbato <lu_zero@g.o> wrote: |
4 |
>>> A whole bunch of science packages have upstreams that say "If you're |
5 |
>>> building from source, run 'make check' and if it fails don't carry |
6 |
>>> on". |
7 |
>> Their rationale behind that is that their code is severely broken, |
8 |
>> using experimental features from their language of choice or, simply, |
9 |
>> that they are paranoid and couldn't think better ways to annoy people? |
10 |
> |
11 |
> Their rationale being that compilers and users screw up, and that |
12 |
> detecting a failure before deployment is important for people who care |
13 |
> about what programs do. |
14 |
> |
15 |
> Simple example... Take people who use Roy's broken patches from bug |
16 |
> 192403. If you build a program that uses C++ exception handling using |
17 |
> such a compiler, it'll compile just fine and then do very weird things |
18 |
> at runtime. Test suites catch this, and spare a lot of everyone's time. |
19 |
|
20 |
You are supposed to test proposed patches for opened bugs before |
21 |
deploying them in any way. |
22 |
|
23 |
Your "example", that btw is a quite low try to smear Roy, proves nothing. |
24 |
|
25 |
> And saving your ass when you're using a broken compiler that generates |
26 |
> broken code that would force you to reinstall a working compiler by |
27 |
> hand when the package manager gets h0rked. |
28 |
|
29 |
You (upstream) are supposed to test and early users are supposed to |
30 |
check their bleeding edge stuff is working if they care enough. |
31 |
People using released programs that are in stable shouldn't have to do |
32 |
that. If your code doesn't survive a gcc release usually it's the code |
33 |
being wrong most of the times. |
34 |
|
35 |
lu |
36 |
|
37 |
-- |
38 |
|
39 |
Luca Barbato |
40 |
Gentoo Council Member |
41 |
Gentoo/linux Gentoo/PPC |
42 |
http://dev.gentoo.org/~lu_zero |
43 |
|
44 |
-- |
45 |
gentoo-dev@l.g.o mailing list |