From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Dennis.Herbrich@hytera.de
Subject: Re: [ptxdist] How to add docs to target without going insane
Date: Tue, 20 Aug 2013 20:59:23 +0200 [thread overview]
Message-ID: <20130820185923.GP30496@pengutronix.de> (raw)
In-Reply-To: <201308191518.48691.jbe@pengutronix.de>
On Mon, Aug 19, 2013 at 03:18:48PM +0200, Jürgen Beisert wrote:
> Hi Dennis,
>
> On Thursday 15 August 2013 12:56:00 Dennis.Herbrich@hytera.de wrote:
> > Greetings to the list!
> >
> > We're creating a not-quite-embedded Linux with the help of the current
> > ptxdist version, and it annoys me to no end to not have the manpages
> > of all those nifty diagnostic tools available on the target. I have to
> > admit I do not know all the tcpdump switches by heart, and neither do
> > the poor sods who else attempt to diagnose problems on the target,
> > and an internet connection isn't always available.
> >
> > Long story short: How do I elegantly package all included documentation
> > for all installed packages for deployment on the target?
> > I don't care if the docs are included in their respective package, or
> > in one huge "manpages.ipk".
> >
> > I do not see myself effectively replacing EVERY upstream rule file, as
> > that would be an obvious maintenance nightmare (unless that patch
> > torrent would be accepted upstream ;)), and picking stuff from
> > the build-target directories seems too much guesswork for my taste.
> > The app's "make install" still knows best what to install where.
>
> Package's "install" stage should also install the man pages (only if enabled,
> for most packages we try to avoid it, because it takes too much time and
> nobody uses the man pages on the target).
> Take a look into the
> corresponding "platform-<platform>/packages/<package>[/usr]/share/man"
> directories. If there are man pages installed you can adapt the package's rule
Also you can read them from there using
man -l -Tutf-8 platform-<platform>/packages/<package>/usr/share/man/man1/tralala.1 | less
(untested).
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2013-08-20 18:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 10:56 Dennis.Herbrich
2013-08-19 13:18 ` Jürgen Beisert
2013-08-20 18:59 ` Uwe Kleine-König [this message]
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=20130820185923.GP30496@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=Dennis.Herbrich@hytera.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