public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thomas Kahle <tomka@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] dev-cpp/gtest
Date: Sun, 30 Jun 2013 15:03:29 +0200	[thread overview]
Message-ID: <51D02CA1.8000203@gentoo.org> (raw)

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

Hi,

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.

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?

a) Drop the library from the ebuild and break most of the consumers who
don't follow upstreams recommendation.
b) Install shared library and sources giving maintainers the choice to
follow upstreams instructions or not.

Here's a list of packages that have gtest in their deps:

app-i18n/librime
app-i18n/mozc
app-text/dvisvgm
dev-cpp/glog
dev-cpp/gmock
dev-cpp/pficommon
dev-games/aseprite
dev-libs/msgpack
dev-util/ninja
dev-util/open
kde-misc/socket
media-libs/audiofile
media-libs/chromaprint
sci-libs/flann
sci-libs/trilinos
sys-apps/paludis

Cheers,
Thomas


-- 
Thomas Kahle


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

             reply	other threads:[~2013-06-30 13:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-30 13:03 Thomas Kahle [this message]
2013-07-15  9:25 ` [gentoo-dev] dev-cpp/gtest "Paweł Hajdan, Jr."
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=51D02CA1.8000203@gentoo.org \
    --to=tomka@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