[MacPorts] #48800: gtest: please remove
#48800: gtest: please remove --------------------------+--------------------- Reporter: ryandesign@… | Owner: blair@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: gtest --------------------------+--------------------- Please remove the gtest port. We previously had this software in MacPorts as "google-test" but removed it in r115909; the developers of Google Test do not want package managers to distribute it. Instead, a private copy should be included in each project that wants to use it. -- Ticket URL: <https://trac.macports.org/ticket/48800> MacPorts <https://www.macports.org/> Ports system for OS X
#48800: gtest: please remove ---------------------------+--------------------- Reporter: ryandesign@… | Owner: blair@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gtest | ---------------------------+--------------------- Comment (by blair@…): Yes, I read that too. However, it's in Ubuntu: {{{ $ apt-cache show libgtest-dev Package: libgtest-dev Priority: optional Section: libdevel Installed-Size: 1302 Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> Original-Maintainer: Steve M. Robbins <smr@debian.org> Architecture: all Source: gtest Version: 1.6.0-1ubuntu6 Filename: pool/main/g/gtest/libgtest-dev_1.6.0-1ubuntu6_all.deb Size: 262206 MD5sum: 3952cdc66cdead128769b18d13df4bd7 SHA1: d47ddbabd85abc4c6ba6ae4f54b7aefd3782f54e SHA256: 144e70bde71d5894da4cf8a4762a88cc5ca97df6b374828e59c83168151c7916 Description-en: Google's framework for writing C++ tests - header files Google's framework for writing C++ tests on a variety of platforms. Based on the xUnit architecture. Supports automatic test discovery, a rich set of assertions, user-defined assertions, death tests, fatal and non-fatal failures, value- and type-parameterized tests, various options for running the tests, and XML test report generation. . This package contains the header files needed to link programs against gtest. Description-md5: 91f80794a8414047791bb3f205c9aa39 Multi-Arch: foreign Homepage: http://code.google.com/p/googletest/ Bugs: https://bugs.launchpad.net/ubuntu/+filebug Origin: Ubuntu Supported: 9m }}} And the instructions for installing grpc, Google's RPC system installs it: https://github.com/grpc/grpc/blob/master/INSTALL In fact, they install it into /opt/local, which is why I want to have a package do it: {{{ $ sudo /opt/local/bin/port install autoconf automake libtool gflags cmake $ mkdir ~/gtest-svn $ svn checkout http://googletest.googlecode.com/svn/trunk/ gtest-svn $ mkdir mybuild $ cd mybuild $ cmake ../gtest-svn $ make $ make gtest.a gtest_main.a $ sudo cp libgtest.a libgtest_main.a /opt/local/lib $ sudo mkdir /opt/local/include/gtest $ sudo cp -pr ../gtest-svn/include/gtest /opt/local/include/gtest }}} So unless there's good reason otherwise, I'll close this. -- Ticket URL: <https://trac.macports.org/ticket/48800#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X
#48800: gtest: please remove ---------------------------+--------------------- Reporter: ryandesign@… | Owner: blair@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gtest | ---------------------------+--------------------- Comment (by ryandesign@…): The Google Test Makefile contains these comments: {{{ # Disables 'make install' as installing a compiled version of Google # Test can lead to undefined behavior due to violation of the # One-Definition Rule. }}} And this line: {{{ echo "'make install' is dangerous and not supported. Instead, see README for how to integrate Google Test into your build system." }}} This seems to make clear that a package manager like MacPorts should not include Google Test, nor should any other means be used to install Google Test into a public location. Projects should only use private copies of Google Test in their build systems for testing. The developers of GRPC should be directed to these facts and advised to include a copy of Google Test in their project, and not advocate installing Google Test into the MacPorts prefix. -- Ticket URL: <https://trac.macports.org/ticket/48800#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X
#48800: gtest: please remove ---------------------------+--------------------- Reporter: ryandesign@… | Owner: blair@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gtest | ---------------------------+--------------------- Comment (by ryandesign@…): They also have a [https://code.google.com/p/googletest/wiki/FAQ #Why_is_it_not_recommended_to_install_a_pre-compiled_copy_of_Goog FAQ entry] on this topic. -- Ticket URL: <https://trac.macports.org/ticket/48800#comment:3> MacPorts <https://www.macports.org/> Ports system for OS X
#48800: gtest: please remove ---------------------------+--------------------- Reporter: ryandesign@… | Owner: blair@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: gtest | ---------------------------+--------------------- Comment (by blair@…): I would agree with you, except that Ubuntu provides it also. Also, the developers of GRPC is Google ;) In the end, I'm not going to remove the package. I don't think it's the end of the world to keep it there. -- Ticket URL: <https://trac.macports.org/ticket/48800#comment:4> MacPorts <https://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts