Amanda Waite wrote:
>
> Attached is the draft Arc case for updating Lighttpd in SFW. I felt this 
> was needed as it covers the following:
> 
> - Obsolescence of spawn-fcgi in the Lighttpd packages

The key question is, is any supported functionality or public interface
of spawn-fcgi is changing or going away (location aside)?

As noted in the case, the lighttpd package will depend on the
spawn-fcgi package, so as far as the user is concerned do they still
get all the same functionality when installing lighttpd?



> - Addition of OpenLDAP and Lua as imported interfaces

See the OpenLDAP thread for comments on importing it from lighttpd.


>     2.4 Changes to the configuration file
> 
>     At the request of the upstream Lighttpd community this case will remove
>     the line:
> 
>     server.max-workers = 4
> 
>     From the Lighttpd configuration file. Running Lighttpd with multiple 
>     workers is not supported by the upstream community.

What about upgrades? Will upgrading previous installation of lighttpd
with this future package remove (or ignore) max-workers or will it
continue to work as before? If the latter, does that now lead to an
unsupported scenario or do you expect to continue supporting it (for
upgrading users only)?



>     The Lighttpd SUNWlighttpd14u package will include a dependency
>     on the spawn-fcgi package and will provide symbolic links from
>     the existing locations of the executable and manpage to the
>     locations delivered by the spawn-fcgi package, i.e.:
> 
>     /usr/lighttpd/1.4/bin/spawn-fcgi -> /usr/bin/spawn-fcgi

So looks like only the /usr/lighttpd/1.4/bin/spawn-fcgi path is being
obsoleted?

What will be the future impact on users when the symlink goes away in
a future release of lighttpd?

Alternatively, does the symlink need to go away? Is there a benefit to
continue to carry the symlink indefinitely? Does it make users life
easier in the long run or is it itself an oddity (i.e. all Linux users
are expecting /usr/bin/spawn-fcgi anyway) in which case it is good to
get it on the obsolete road.


-- 
Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems

Reply via email to