| 1 |
Mike Z. wrote: |
| 2 |
> Definitely, compilation is fine, but you need to have some sort of |
| 3 |
> runtime testing as well. On the note of libraries, I would think, rather |
| 4 |
> than keywording libraries that compile, we should wait until an |
| 5 |
> application that requires them also needs to be keyworded. This will |
| 6 |
> probably depend on which library it is, but it'd mean that we have a |
| 7 |
> full deptree for each application, as well as a useful real-world test |
| 8 |
> case. |
| 9 |
|
| 10 |
This is in general the case. We cannot keyword a library without having |
| 11 |
it tested. My keyword for mp (the editor) was an example of this, I |
| 12 |
needed something small to test libpcre. I think when people report a |
| 13 |
library working/compiling, they use the library in some application. |
| 14 |
Maybe that application is not in portage, or so big that it isn't an |
| 15 |
appropriate test case, but I'd still like to keyword (unstable) |
| 16 |
libraries before a separate bug for an application using the library is |
| 17 |
there, because it's enormously annoying to have to keyword a whole tree |
| 18 |
of dependencies to figure out the 6th level dependency does not and will |
| 19 |
never compile. |
| 20 |
|
| 21 |
|
| 22 |
-- |
| 23 |
Fabian Groffen |
| 24 |
Gentoo for Mac OS X |
| 25 |
-- |
| 26 |
gentoo-osx@g.o mailing list |
Archives