1 |
On 25/08/2005, at 3:36 PM, Grobian wrote: |
2 |
|
3 |
>> |
4 |
>> |
5 |
> |
6 |
> Another thing that crossed my mind when going to work this morning: |
7 |
> |
8 |
> When people submit bugs for working/new packages, they usually tell it |
9 |
> works fine, or in some cases that they applied a little patch to |
10 |
> get it |
11 |
> working. However, before even thinking of keywording, I want to know |
12 |
> whether the package reasonably works. That means, I want to do |
13 |
> some small |
14 |
> sanity check, or just functional check that the application or library |
15 |
> appears to work as expected. I think you cannot expect any dev to |
16 |
> know |
17 |
> every package in portage, let alone being common with using it. So |
18 |
> I'd |
19 |
> propose to add a little note on the "reporting bugs" section that |
20 |
> asks the |
21 |
> users to -- if they can come up with it: |
22 |
> 1) in case of an application tell us how you can test it works: |
23 |
> example, |
24 |
> streamripper, do streamripper http://some.host.com/music path/to/ |
25 |
> bla.mp3, |
26 |
> listen to the mp3, it appears to work fine |
27 |
> 2) in case of a library tell us what application can be used to |
28 |
> test it, |
29 |
> preferable small and direct: example, libpcre, emerge mp with USE flag |
30 |
> pcre, start mp on a file, press Ctrl-a navigate in the menu to search, |
31 |
> type a regular expression search like .(build|merge|keyword)+, |
32 |
> check it |
33 |
> matches an appropriate string |
34 |
> |
35 |
|
36 |
Definitely, compilation is fine, but you need to have some sort of |
37 |
runtime testing as well. On the note of libraries, I would think, |
38 |
rather than keywording libraries that compile, we should wait until |
39 |
an application that requires them also needs to be keyworded. This |
40 |
will probably depend on which library it is, but it'd mean that we |
41 |
have a full deptree for each application, as well as a useful real- |
42 |
world test case. |
43 |
|
44 |
Mike Z. [shootingstar] |
45 |
|
46 |
|
47 |
-- |
48 |
gentoo-osx@g.o mailing list |