From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Date: Tue, 20 Aug 2013 20:59:23 +0200 From: Uwe =?iso-8859-1?Q?Kleine-K=F6nig?= Message-ID: <20130820185923.GP30496@pengutronix.de> References: <201308191518.48691.jbe@pengutronix.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <201308191518.48691.jbe@pengutronix.de> Subject: Re: [ptxdist] How to add docs to target without going insane Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de Cc: Dennis.Herbrich@hytera.de On Mon, Aug 19, 2013 at 03:18:48PM +0200, J=FCrgen 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 enab= led, = > 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-/packages/[/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-/packages//usr/share/man/man1/t= ralala.1 | less (untested). Best regards Uwe -- = Pengutronix e.K. | Uwe Kleine-K=F6nig | Industrial Linux Solutions | http://www.pengutronix.de/ | -- = ptxdist mailing list ptxdist@pengutronix.de