public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "\"Paweł Hajdan, Jr.\"" <phajdan.jr@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] dev-cpp/gtest
Date: Mon, 15 Jul 2013 11:25:54 +0200	[thread overview]
Message-ID: <51E3C022.5010304@gentoo.org> (raw)
In-Reply-To: <51D02CA1.8000203@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]

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ł


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 203 bytes --]

  reply	other threads:[~2013-07-15  9:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-30 13:03 [gentoo-dev] dev-cpp/gtest Thomas Kahle
2013-07-15  9:25 ` "Paweł Hajdan, Jr." [this message]
2013-07-15 13:12 ` [gentoo-dev] dev-cpp/gtest Steven J. Long

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51E3C022.5010304@gentoo.org \
    --to=phajdan.jr@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox