Thank you for the quick reply.
[Guillem Jover]
> I've not checked those bug reports, but I'm assuming that the
> package might also fail in case apache2 is not installed at all? Or
> how do you handle that case? And the subsequent missing
> configuration when apache2 gets installed later on?
For sitesummary, the package do not fail if apache2 is not installed
at all. The postinst fragment look like this:
case "$1" in
configure)
# Enable it on fresh installations as before Apache 2.4.
if [ -z "$2" ] && \
[ -e /usr/share/apache2/apache2-maintscript-helper ] ; then
. /usr/share/apache2/apache2-maintscript-helper
apache2_invoke enmod cgi.load
apache2_invoke enconf sitesummary.conf
fi
If the apache2 package isn't installed unpacked yet, the sitesummary
collector CGI script will simply not be activated by default.
I do not know how the svn stuff handle the case.
> I think using triggers would solve all your problems. It would also
> cover the case where a user installs sitesummary, but not apache2,
> and later on installs apache2. You might need to coordinate with the
> apache2 team to create possibly an explicit trigger name for
> this. Or would that not solve your problem?
The reason apache2 is only a recommends is to ensure other web servers
can be used with sitesummary, and that the sitesummary server scripts
can be used without a web server active. I am not sure it is a good
idea to activate sitesummary automatically outside the initial
installaiton, and thus unsure if the trigger approach is the right
one. But I will investigate.
--
Happy hacking
Petter Reinholdtsen
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
