From: Leo Famulari <leo@famulari.name>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add capnproto.
Date: Fri, 19 Aug 2016 18:06:24 -0400 [thread overview]
Message-ID: <20160819220624.w5wu4c47ltzpud4u@jasmine> (raw)
In-Reply-To: <87wpjjgqrt.fsf@ike.i-did-not-set--mail-host-address--so-tickle-me>
On Sun, Aug 14, 2016 at 07:16:22PM +0100, Marius Bakke wrote:
> Leo Famulari <leo@famulari.name> writes:
>
> > On Sat, Aug 13, 2016 at 07:48:36PM +0100, Marius Bakke wrote:
> >> Note that it bundles googletest; I tried unbundling but it proved
> >> difficult. gtest will no longer be used from the 0.6 release so I did
> >> not think a comment was necessary.
> >
> > I am cc-ing Lukas with my reply, since he added our googletest package.
> > Maybe he has some insight.
> The problem is that their autotools system expects to build gtest as
> well, so there are references all over. See:
> https://github.com/sandstorm-io/capnproto/blob/release-0.5.3/c%2B%2B/Makefile.am
> and also configure.ac. It would have to be patched out, which seems
> excessive for a 4MB build dependency.
In my opinion, it's generally not about the size of the bundled
dependency. Rather, it's about the opacity of the dependency graph of
the application that does the bundling. The worst case would be
something like a bundled OpenSSL, for example.
In this case, Debian has accepted the bundled gtest [0], which makes me
wonder if my understanding of gtest is incorrect. Perhaps it is designed
to be bundled?
[0]
https://packages.debian.org/sid/devel/capnproto
next prev parent reply other threads:[~2016-08-19 22:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-13 18:48 [PATCH] gnu: Add capnproto Marius Bakke
2016-08-14 17:17 ` Leo Famulari
2016-08-14 18:16 ` Marius Bakke
2016-08-19 22:06 ` Leo Famulari [this message]
2016-08-19 22:17 ` Leo Famulari
2016-08-20 12:22 ` Marius Bakke
2016-08-23 16:00 ` Leo Famulari
2016-08-23 18:30 ` Marius Bakke
2016-08-23 18:40 ` Leo Famulari
-- strict thread matches above, loose matches on Subject: below --
2016-08-25 8:04 Kenton Varda
2016-08-25 14:57 ` Marius Bakke
2016-08-25 17:22 ` Kenton Varda
2016-08-25 15:32 ` Alex Vong
2016-08-25 15:52 ` Marius Bakke
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160819220624.w5wu4c47ltzpud4u@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).