From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] help broken again since 2016.10.0
Date: Thu, 1 Dec 2016 11:02:45 +0100 [thread overview]
Message-ID: <20161201100245.i7yx2re6xfqvzlpi@pengutronix.de> (raw)
In-Reply-To: <49ceee5249f35c1fac10f54ede9a77a3@idefix.home.lespocky.de>
Hi,
On Wed, Nov 23, 2016 at 09:48:39AM +0100, Alexander Dahl wrote:
> while searching how to build the new documentation (btw: I could not
> find out) I stumbled over the broken help. Results from different
> ptxdist versions:
>
[...]
>
> The file ptxdist.1.gz is only available in the folders of 2016.08.0 and
> 2016.09.0 and missing in all the others. I usually install like this:
>
> * go to ptxdist src folder (git clone)
> * git co ptxdist-201?-??-?
> * git clean -dxf
> * ./autogen.sh
> * ./configure
> * make
> * sudo make install
>
> In the current master no man page is created with a simple `make`, I
> would have to call `make man`, not sure if it gets installed, though,
> didn't test it.
This was a deliberate change and I'm not quite sure how to improve the
situation.
I did not want to make rst2man a hard requirement for ptxdist. So all
tarball releases contain the man-page.
I suppose we could create the man page under certain circumstances during
'make'. What should the condition be? If rst2man is found? When working
with a ptxdist git checkout?
Regards,
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2016-12-01 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 8:48 Alexander Dahl
2016-12-01 10:02 ` Michael Olbrich [this message]
2016-12-01 10:19 ` Uwe Kleine-König
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=20161201100245.i7yx2re6xfqvzlpi@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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