On 6/30/13 3:03 PM, Thomas Kahle wrote: > dev-cpp/gtest is Google's testing framework. According to upstream it > is supposed to be shipped as source code and then compiled by the build > system of the software that should be tested. In particular it should > be compiled with exactly the same flags.
That's correct, and I consider that design broken. They could have easily provided an executable like gtest-config or even just use pkg-config to provide proper flags to compile the dependent sources. > So far our gtest package has shipped only the compiled library and a > bunch of helper scripts. Now bug 474454 asks for the sources to be > installed too (or exclusively). What should we do? IMHO a package that installs sources makes no sense. Anything that would use it would be highly non-standard - this was not indended to be shared. I'd rather schedule dropping the package and make reverse dependencies use bundled gtest (upstream intends this to be used as a copylib). In the long term it could be worth it to convince upstream to do something more sane and standard. It is technically possible. Paweł
signature.asc
Description: OpenPGP digital signature
