all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alex Vong <alexvong1995@gmail.com>
To: Kenton Varda <kenton@sandstorm.io>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add capnproto.
Date: Thu, 25 Aug 2016 23:32:57 +0800	[thread overview]
Message-ID: <87a8g0vp7a.fsf@gmail.com> (raw)
In-Reply-To: <CAOP=4wh+2__kbiRoHy0hdTtdhdRzE-d9fkUhh2mqoHwuK9=p9g@mail.gmail.com> (Kenton Varda's message of "Thu, 25 Aug 2016 01:04:34 -0700")

Hi,

Kenton Varda <kenton@sandstorm.io> writes:

> Hi, Cap'n Proto upstream author here. Noticed this thread in a Google
> search, thought I'd comment.
>
> To shed some light on the googletest situation:
>
> The googletest maintainers have deemed that googletest should never
> ever be system-installed, and have even disabled `make install` in
> their build. See:
>
> https://github.com/google/googletest/blob/master/googletest/Makefile.am#L300
>
> I don't really understand what they think they're solving here but it
> is what it is and this seems to make it hard to use googletest in a
> non-bundled way. It's possible I misunderstood, though.
>
> FWIW, Cap'n Proto only uses googletest to build its tests. It does not
> install any artifacts that were influenced by googletest.
>
> In any case, this dependency will be gone once I find time to do the
> next release. Sorry for the trouble in the meantime.
>
> -Kenton
>
> PS. regarding the man page, I believe Debian mostly generated this
> page from the capnp tool's help text. I'd accept a patch to
> c++/src/kj/main.c++ which adds some code to generate man XML format
> directly, so that we don't have to maintain the same text in multiple
> places.

I want to ask what is meant by man XML format? Do you mean to generate
man page? As far as I know, there are at least 2 ways to generate a man
page. One way is to use help2man, which is probably the Debian's
approach. Another way is to write the man page in pod (perl's plain old
documentation) and use pod2man to translate it into a man page. Would
you accept any of these approaches?

Thanks,
Alex

  parent reply	other threads:[~2016-08-25 15:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-25  8:04 [PATCH] gnu: Add capnproto Kenton Varda
2016-08-25 14:57 ` Marius Bakke
2016-08-25 17:22   ` Kenton Varda
2016-08-25 15:32 ` Alex Vong [this message]
2016-08-25 15:52   ` Marius Bakke
  -- strict thread matches above, loose matches on Subject: below --
2016-08-13 18:48 Marius Bakke
2016-08-14 17:17 ` Leo Famulari
2016-08-14 18:16   ` Marius Bakke
2016-08-19 22:06     ` Leo Famulari
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

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=87a8g0vp7a.fsf@gmail.com \
    --to=alexvong1995@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=kenton@sandstorm.io \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.