I feel it's too late, but can we split package for web interface?
Advantages I think are:
a user who wants to use web interface but don't want to use prepared HTTPd configurations (e.g. using another server software) may install only sympa and sympa-www below.
replacement of web interface in the future may be easy.
Idea is that sympa-www package including executables, modules etc. for web interface but not including configuration for each HTTP server. For example:
I feel it's too late, but can we split package for web interface?
Advantages I think are:
sympa
andsympa-www
below.Idea is that
sympa-www
package including executables, modules etc. for web interface but not including configuration for each HTTP server. For example:(Note: above is incomplete list.)
Below would be included in
sympa-www
, but are referred to by recent code used by coresympa
package.2018-03-29 Updated file list.