On Tue, Apr 24, 2018 at 4:21 AM, Steve Robbins <st...@sumost.ca> wrote: > On Sunday, April 22, 2018 5:27:07 AM CDT you wrote: >> Package: googletest >> Version: 1.8.0-8 >> Severity: important >> >> Dear maintainer. Now that #868234 has been resolved, >> the package installs sources into /usr/src, >> and the prebuild library, + headers into /usr/include. >> >> This is somewhat problematic. >> Now if one does not want to use the prebuilt library, >> but build it in tree (anyone who cares will do that), >> the headers from the prebuild library will still be in >> the search path. > > I agree it is not optimal. I have prepared a new revision that implements > your suggestion #4. In the upcoming revision: > > Package googletest installs sources only > Package libgtest-dev installs headers + lib for gtest > New package libgmock-dev installs headers + lib for gmock SGTM, thanks.
> Let me know if this works for you. I've just pushed it to Salsa: > https://salsa.debian.org/debian/googletest > > >> There are several solutions: >> 1. Don't provide prebuild library. >> 2. Don't install sources in googletest package, >> tell people to use $ apt-get source. BAD. >> 3. Install headers into some prefix, so they won't be automatically used. >> 4. Keep googletest with only the sources, and package >> built library + headers as a separate package, googletest-prebuilt. >> 5. 3+4 Probably the best one. > > I don't believe #3 is worth the trouble because (a) it breaks the automatic > detection I've seen in some packages; and (b) the headers in /usr/src/googlest > and in /usr/include are identical, so there's no real issue if the latter is > used for a source build. > > Best, > -Steve Roman.
