1 |
"Chris Bainbridge" <chris.bainbridge@×××××.com> posted |
2 |
623652d50607270200h14bae69ai360777afc3d725ae@××××××××××.com, excerpted |
3 |
below, on Thu, 27 Jul 2006 10:00:39 +0100: |
4 |
|
5 |
> The testing is supposed to be for the ebuild, not the package itself, |
6 |
> so there's not much point in holding back packages with simple ebuilds |
7 |
> from being stabilised. |
8 |
|
9 |
While ~arch is supposed to be stable upstream, testing the ebuild, in |
10 |
practice there's more to it than that. "Ebuild" in this case is shorthand |
11 |
for "Gentoo aspects of a package, including not only the ebuild script, |
12 |
but how the build process functions and the interaction with the various |
13 |
available Gentoo gcc/glibc/binutils/etc packages, and how it runs in a |
14 |
Gentoo system, including not only file system layout, but how it actually |
15 |
runs against the various current Gentoo versions of all its dependencies. |
16 |
|
17 |
In fact, a specifically enumerated part of an arch-tester's job is to test |
18 |
not only build-time success, but that it actually runs reasonably well |
19 |
also. While an arch-tester can't be expected to always be familiar enough |
20 |
with the app to test all the little corner cases, when they say it's ready |
21 |
to stabilize, they are in effect reporting that it not only compiled, but |
22 |
ran "as advertised" with no glaring issues or instabilities thru a |
23 |
reasonable test of its runtime functionality as well, such that it should |
24 |
be safe to keyword stable, and therefore be available to those that |
25 |
actually depend on the app for "mission critical" functionality (whether |
26 |
that mission is as a public server, or blasting the other team in an online |
27 |
frag-fest). |
28 |
|
29 |
-- |
30 |
Duncan - List replies preferred. No HTML msgs. |
31 |
"Every nonfree program has a lord, a master -- |
32 |
and if you use the program, he is your master." Richard Stallman |
33 |
|
34 |
-- |
35 |
gentoo-dev@g.o mailing list |