From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: From: Alexander Stein Date: Wed, 23 Jan 2013 13:28:26 +0100 Message-ID: <1690445.GXkacljTTg@ws-stein> In-Reply-To: <20130123112624.GD26180@pengutronix.de> References: <1358936152-14330-1-git-send-email-alexander.stein@systec-electronic.com> <1358936152-14330-2-git-send-email-alexander.stein@systec-electronic.com> <20130123112624.GD26180@pengutronix.de> MIME-Version: 1.0 Subject: Re: [ptxdist] [PATCH 2/2] lighttpd: Add config option to select modules explicitly 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="us-ascii" Content-Transfer-Encoding: 7bit Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de Cc: Michael Olbrich Hello Michael, 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. Best regards, Alexander -- ptxdist mailing list ptxdist@pengutronix.de