Mike Z. wrote:
> Definitely, compilation is fine, but you need to have some sort of 
> runtime testing as well. On the note of libraries, I would think, rather 
> than keywording libraries that compile, we should wait until an 
> application that requires them also needs to be keyworded. This will 
> probably depend on which library it is, but it'd mean that we have a 
> full deptree for each application, as well as a useful real-world test 
> case.

This is in general the case.  We cannot keyword a library without having 
it tested.  My keyword for mp (the editor) was an example of this, I 
needed something small to test libpcre.  I think when people report a 
library working/compiling, they use the library in some application. 
Maybe that application is not in portage, or so big that it isn't an 
appropriate test case, but I'd still like to keyword (unstable) 
libraries before a separate bug for an application using the library is 
there, because it's enormously annoying to have to keyword a whole tree 
of dependencies to figure out the 6th level dependency does not and will 
never compile.


-- 
Fabian Groffen
Gentoo for Mac OS X
-- 
gentoo-osx@g.o mailing list