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