| 1 |
On 5/27/06, Alexander Skwar <listen@×××××××××××××××.name> wrote: |
| 2 |
> >>>if he does not have glib? |
| 3 |
> > |
| 4 |
> >>Then he installs it. |
| 5 |
> > |
| 6 |
> > so, he should install something he does not need and 'test' it, to satisfy |
| 7 |
> > your needs? |
| 8 |
> |
| 9 |
> Not MY needs, no. But to be able to say that all is fine, when it has been |
| 10 |
> posted here, that glib is one of the culprits. |
| 11 |
|
| 12 |
No, this wasn't my point at all. I am *not* arguing that "all is |
| 13 |
fine". (However I still don't see how you figure that a bug report |
| 14 |
that shows the exact same problem occurring with both gcc 3.4.6 and |
| 15 |
4.1.1 indicates a problem with 4.1.1) |
| 16 |
|
| 17 |
My point is that it is wrong to flame the devs about a problem with a |
| 18 |
~arch package. Regardless of any documentation, GWN entries, or |
| 19 |
anything else anybody wrote, the very fact that gcc 4.1 is in ~arch |
| 20 |
means it needed wider testing. Here is what the handbook says about |
| 21 |
the testing branch: |
| 22 |
|
| 23 |
<quote> (http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=3) |
| 24 |
The testing branch is exactly what it says - Testing. If a package is |
| 25 |
in testing, it means that the developers feel that it is functional |
| 26 |
but has not been thoroughly tested. You could very well be the first |
| 27 |
to discover a bug in the package in which case you could file a |
| 28 |
bugreport to let the developers know about it. |
| 29 |
|
| 30 |
Beware though, you might notice stability issues, imperfect package |
| 31 |
handling (for instance wrong/missing dependencies), too frequent |
| 32 |
updates (resulting in lots of building) or broken packages. |
| 33 |
</quote> |
| 34 |
|
| 35 |
You complained about a "complete lack of QA", and it seemed quite |
| 36 |
obvious you were not referring to just the gcc upgrade. Well guess |
| 37 |
what...~arch users _are_ the QA department! If you are not willing to |
| 38 |
try out things that the developers *think* will work, without flaming |
| 39 |
them when you encounter a problem that slipped by, you have no |
| 40 |
business running ~arch. |
| 41 |
|
| 42 |
This whole topic of "this-or-that worked fine for me" was a mistake on |
| 43 |
my part. I was trying to make another point which was that the |
| 44 |
statement claiming "the upgrade should be incredibly easy..." could |
| 45 |
have been perfectly reasonable to make. Unfortunately it has been |
| 46 |
more of a distraction than anything else. |
| 47 |
|
| 48 |
-Richard |
| 49 |
|
| 50 |
-- |
| 51 |
gentoo-user@g.o mailing list |
Archives