From: Joshua Lock <joshua.g.lock at linux.intel.com>
To: tpm2@lists.01.org
Subject: Re: [tpm2] tpm2-tools man pages not installing?
Date: Fri, 06 Jul 2018 14:48:31 +0100 [thread overview]
Message-ID: <f22d1663-c1af-f20e-b4d8-4985074bf2f2@linux.intel.com> (raw)
In-Reply-To: 54a96f1978da464a98e1c4b04420451e@AZDC-MMB02.GD-MS.US
[-- Attachment #1: Type: text/plain, Size: 1857 bytes --]
No need to apologise, we do have plans to review and try to improve the
quality of all of the manual pages. In the interim a Github pull request
would be most welcome.
Joshua
On 05/07/2018 21:44, Scheie, Peter M wrote:
> BTW, there's a grammatical error in the man page for tpm2_unseal. What's the best way to get that fixed? (Sorry, my mother was an English major).
>
> Peter
>
> -----Original Message-----
> From: Joshua Lock [mailto:joshua.g.lock(a)linux.intel.com]
> Sent: Wednesday, July 04, 2018 5:10 AM
> To: Matthias Gerstner; Scheie, Peter M
> Cc: tpm2(a)lists.01.org
> Subject: Re: [tpm2] tpm2-tools man pages not installing?
>
>
>
> On 03/07/2018 15:53, Matthias Gerstner wrote:
>> Hello,
>>
>> On Tue, Jul 03, 2018 at 01:46:14PM +0000, Scheie, Peter M wrote:
>>> When I build & install tpm2-tools, the man pages don't seem to get
>>> installed. I'm just using the default './configure; make; sudo make
>>> install' routine, so everything is going into /usr/local/; therefore,
>>> I'd expect the man pages to end up in /usr/local/share/man, but they
>>> don't. Do I need add an argument to configure to make that happen?
>>
>> that is actually a bug and I addressed it via commit
>> 72a28f36151db9bfa59a460ae0114dcece218862, however that commit didn't
>> make it into the current release.
>>
>> So you either have to install them manually or, as a workaround, if you
>> have pandoc installed on the system, then the build system tries to
>> generate the man pages and alongside that also installs them.
>
> Thanks for the report Peter and for pointing to the fix Matthias. I've
> backported the change to the 3.X branch and tagged a release candidate
> for 3.1.1 which includes the fix:
>
> https://github.com/tpm2-software/tpm2-tools/releases/tag/3.1.1-rc0
>
> Regards,
> Joshua
>
next reply other threads:[~2018-07-06 13:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 13:48 Joshua Lock [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-06 17:30 [tpm2] tpm2-tools man pages not installing? Scheie, Peter M
2018-07-06 17:12 Roberts, William C
2018-07-06 15:19 Scheie, Peter M
2018-07-06 14:10 Scheie, Peter M
2018-07-05 20:44 Scheie, Peter M
2018-07-04 10:09 Joshua Lock
2018-07-03 17:49 Philip Tricca
2018-07-03 17:41 Scheie, Peter M
2018-07-03 14:53 Matthias Gerstner
2018-07-03 13:46 Scheie, Peter M
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=f22d1663-c1af-f20e-b4d8-4985074bf2f2@linux.intel.com \
--to=tpm2@lists.01.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