From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Feature Request: Option to install man pages
Date: Wed, 04 Mar 2015 20:18:09 +0100 [thread overview]
Message-ID: <54F75A71.4000905@lespocky.de> (raw)
In-Reply-To: <54F6E22E.3080209@gmx.net>
[-- Attachment #1.1: Type: text/plain, Size: 1068 bytes --]
Hei hei,
Am 04.03.2015 um 11:45 schrieb Carsten Schlote:
> I know, it is intentional to save precious memory on embedded devices
> with usually small flash devices storing the firmware. 'Small' ment
> something in the few MB range running compressed MTD filesystems.
>
> The ability to create small rootfs images was basically my primary
> reason to use ptxdist many years ago, when I had just 32 MB of flash for
> all and everything.
And this is still the case. The main device we use ptxdist for (and
probably will for the next years) has 32 MB RAM and 256 MB Flash with an
actual root partition of around 40 MB.
> So I would like to propose to add some global switch to the ptxdist
> configuration, which optionally allows users to install docs. Docs
> usually mean man pages, but options for info or similar would be fine,
> too. And of course a set of macros for the targetinstall stage, which
> conditionally picks up man pages at the usual places, when enabled.
[…]
> Your opinions?
Please make it optional.
Greets
Alex
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 48 bytes --]
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2015-03-04 19:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 10:45 Carsten Schlote
2015-03-04 12:14 ` Rüdiger, Christoph
2015-03-04 18:40 ` Bruno Thomsen
2015-03-04 19:18 ` Alexander Dahl [this message]
2015-03-05 12:59 ` Guillermo Rodriguez
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=54F75A71.4000905@lespocky.de \
--to=post@lespocky.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