Re: [ITA] lighttpd

[Achim Gratz <Stromeko@nexgo.de>]

Glenn Strauss writes:
> lighttpd is a modular web server.  However, the current lighttpd.cygport
> lumps *everything* together into a single package, with dependencies for
> all modules.  It appears the same was done for nginx.  At least Apache
> httpd.cygport has multiple packages.  I plan to do something similar for
> lighttpd-1.4.56, as lighttpd-1.4.56 adds multiple options for TLS
> libraries, and a single lighttpd package should not depend on many
> different TLS libraries available under Cygwin.  While lighttpd "could"
> do so, I would rather not do so for those for whom disk space matters.
>
> Question: what is the recommended approach to deploying such a change?

You either just strip down the functionality of the previous package to
something lean enough but having the typical functionality you think
most users will need _or_ you obsolete the previous package and then
have a bunch of new packages that do whatever you want.  The obsoletion
needs to name a suggested replacement.

> The lighttpd base package will still contain all modules for typical
> usage of lighttpd.  However, if an end-user is using mod_openssl and
> TLS modules are separated into separate packages, then the additional
> package would need to be installed.

Keep in mind that setup currently gives no hints on such optional
dependencies and when they are needed.

> On Debian, this transition is occurring by having the Debian lighttpd
> package "Recommends" lighttpd-mod-openssl, and apt/dpkg will install
> the openssl module for typical upgrades which accept "Recommends".
>
> Is there any similar mechanism on Cygwin?

No, in part because there is no way for setup to ask the user and use
the answer.  The libsolv that does the actual package selection could do
that, but we don't deliver the inputs.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada