From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 2/2] lighttpd: Add config option to select modules explicitly
Date: Fri, 25 Jan 2013 10:47:25 +0100 [thread overview]
Message-ID: <20130125094725.GA11534@pengutronix.de> (raw)
In-Reply-To: <1690445.GXkacljTTg@ws-stein>
Hi,
On Wed, Jan 23, 2013 at 01:28:26PM +0100, Alexander Stein wrote:
> On Wednesday 23 January 2013 12:26:24, Michael Olbrich wrote:
> > What's the usecase for this? This are a lot of options and hard to
> > maintain. And the plugins are so small, that I don't think it's worth it to
> > save the space.
>
> That's exactly the use case. On that particular board we don't have much
> flash memory available, so even reducing about 1,4 MiB is essential in that
> case.
> You can at least get a list of the modules when the package is installed using this shell command:
> > for mod in platform/packages/lighttpd-1.4.31/usr/lib/lighttpd/*.so; do MOD=$(basename $mod); echo ${MOD/.so/}; done
> This could be a starting point to create e.g. a lighttpd_modules.in by a script which includes this options.
I've pushed my lighttpd rework that I've been working on for some time. You
can now explicitly select some modules (those that require extra
dependencies etc.). For the rest there is a string to add them manually.
The list will be added for loading to the config file, and optionally used
to only install these modules.
Does this work for you?
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:[~2013-01-25 9:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 10:15 [ptxdist] [PATCH 1/2] lighttpd: Bump to version 1.4.31 Alexander Stein
2013-01-23 10:15 ` [ptxdist] [PATCH 2/2] lighttpd: Add config option to select modules explicitly Alexander Stein
2013-01-23 11:26 ` Michael Olbrich
2013-01-23 12:28 ` Alexander Stein
2013-01-25 9:47 ` Michael Olbrich [this message]
2013-01-28 13:14 ` Alexander Stein
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=20130125094725.GA11534@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