On 25/11/2016 23:34, Mathy Vanvoorden wrote:
>     AFAIK they are not intended to be installed as compiled code at all.
>     You are supposed to bundle them, or otherwise compile them from sources
>     along with your project.
> 
> 
> You are correct, apparently they changed their stance on this some time
> ago as you can read here:
> 
> https://github.com/google/googletest/blob/master/googletest/docs/FAQ.md#why-is-it-not-recommended-to-install-a-pre-compiled-copy-of-google-test-for-example-into-usrlocal
> 
> They also no longer support the autotools scripts that are provided with
> the source code as you can read in the README:
> 
> https://github.com/google/googletest/blob/master/googletest/README.md#legacy-build-scripts
> 
> There are quite some packages depending on them so they can't just be
> last-rited. Maybe the best solution is to leave them in their current
> form (perhaps update the SRC_URI) and not accepting package updates to
> 1.8, instead asking upstream packages that depend on them to include
> them in their source distribution.

I agree with that plan.  The release files provided here
https://github.com/google/googletest/releases seem to have different
md5sums from the one that were shipped on googlecode.  It is painful to
replace those files on the mirrors.  So the best solution is probably to
host the <1.8 release files on a devspace (like mine).

If you want to work on this, maybe you could open bugs / contact the
maintainers of the packages that depend on gtest/gmock.  As you say,
this is not really a package a distribution should ship.

Cheers,
Thomas

> 
> 
> br,
> Mathy

-- 
Thomas Kahle
http://dev.gentoo.org/~tomka/