1 |
Hi, |
2 |
|
3 |
Alexis Ballier <aballier@g.o>: |
4 |
> > 4) Nobody knows how work all packages in tree, so there are obvious |
5 |
> > packages like a browsers, IM, audio player,that is easy decide if is |
6 |
> > ok or not, but there are also packages that an Arch tester has never |
7 |
> > seen, so is a lack of time everytime google about it or ask to |
8 |
> > maintainer, so, please specify what test you want for this package; |
9 |
> > e.g. -only compile test |
10 |
> > -compile test and make sure src_test goes well |
11 |
> > -make sure /usr/bin/${foo} works properly in ${that} manner |
12 |
> > -see 5) about library |
13 |
> > |
14 |
> > So, you can write one time 'how to' and copy/paste for the future |
15 |
> > stablereq; I guess I'm not asking a long and difficult task. |
16 |
> |
17 |
> what i dislike in this approach is that arch testers will follow a |
18 |
> test plan which the maintainer has obviously tested before and knows |
19 |
> it works. |
20 |
> sending people into the jungle of 'try to do something with $pkg' may |
21 |
> make them encounter problems the maintainer hadnt thought about. |
22 |
|
23 |
To stick with the Emacs example: We barely use all those packages we |
24 |
maintain. So sometimes we do not even execute this documented |
25 |
test plan ourselves. Of course it only contains a small subset of |
26 |
everything, but some test plans contain a "fool around with the |
27 |
program" and it is better than nothing. |
28 |
|
29 |
V-Li |
30 |
|
31 |
-- |
32 |
Christian Faulhammer, Gentoo Lisp project |
33 |
<URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode |
34 |
|
35 |
<URL:http://gentoo.faulhammer.org/> |