From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 0EB981381F3 for ; Mon, 15 Jul 2013 09:26:06 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 75037E0784; Mon, 15 Jul 2013 09:25:59 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id A5025E09B9 for ; Mon, 15 Jul 2013 09:25:58 +0000 (UTC) Received: from phjr-macbookpro.local (hmz130.internetdsl.tpnet.pl [79.188.77.130]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: phajdan.jr) by smtp.gentoo.org (Postfix) with ESMTPSA id 6A6CC33E874 for ; Mon, 15 Jul 2013 09:25:57 +0000 (UTC) Message-ID: <51E3C022.5010304@gentoo.org> Date: Mon, 15 Jul 2013 11:25:54 +0200 From: =?UTF-8?B?IlBhd2XFgiBIYWpkYW4sIEpyLiI=?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] dev-cpp/gtest References: <51D02CA1.8000203@gentoo.org> In-Reply-To: <51D02CA1.8000203@gentoo.org> X-Enigmail-Version: 1.5.1 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2PWIGQMLUDOPCWRIIPTRD" X-Archives-Salt: cc17f895-07e7-4a85-bc62-280cbf6dbd6e X-Archives-Hash: 49cbb12f393a1b045eef743ad152bc43 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ------enig2PWIGQMLUDOPCWRIIPTRD Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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=C5=82 ------enig2PWIGQMLUDOPCWRIIPTRD Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) iEYEARECAAYFAlHjwCIACgkQuUQtlDBCeQJ2KACeO8ud5EhE5Z4OiX/9XXZwySuX PXQAn26qkRN9rsHH2CH/PpX/A8Iie+Cw =zWB6 -----END PGP SIGNATURE----- ------enig2PWIGQMLUDOPCWRIIPTRD--