1 |
On Fri, August 26, 2005 08:04, Mike Z. wrote: |
2 |
> That wasn't exactly my point, my point was that we should hold off |
3 |
> keywording libraries until they will actually be used by an |
4 |
> application that is keyworded, and hence properly tested. |
5 |
|
6 |
eh, yes |
7 |
|
8 |
> With libraries it's important to consider what will actually be |
9 |
> compiled against them (the reverse deptree) - ie, the library might |
10 |
> compile, but how do we know applications will compile/run against it? |
11 |
|
12 |
eh, yes, currently we require at least one application to compile/run |
13 |
against the library (we call it 'testing' I think) |
14 |
|
15 |
> Well in that case, we have to test them... and if we've tested them |
16 |
> (assuming they pass, or are modified to pass), then we can keyword them. |
17 |
|
18 |
which is what we do |
19 |
|
20 |
> I'm only suggesting that it makes more sense to test/keyword |
21 |
> libraries with applications, rather than on their own. |
22 |
|
23 |
We (at least I) don't keyword a library that has no application which uses |
24 |
the library, to be sure there is at least one program that was happy when |
25 |
using the library. It's impossible to do an exhaustive test of all |
26 |
applications using the library. That's where my testing proposal was for. |
27 |
|
28 |
I get your concerns, but I don't think they are valid, as I think we deal |
29 |
with libraries as you propose. That's why keywording libraries suck, you |
30 |
need to do at least two things: 1) getting the library to compile/install |
31 |
and 2) finding/testing with an application that uses the library (which |
32 |
may not be that obvious like pcre). |
33 |
|
34 |
I think that whenever we keyword a library, it usually is part of a larger |
35 |
tree of packages depending upon each other. Since the dependencies should |
36 |
be keyworded before the depending package (portage policy), and we don't |
37 |
want the dependency around before the package that depends on it |
38 |
(testing), we end up in an 'atomic' commit where both library and |
39 |
application are keyworded at once. |
40 |
|
41 |
-- |
42 |
gentoo-osx@g.o mailing list |