http://bugzilla.suse.com/show_bug.cgi?id=941331
http://bugzilla.suse.com/show_bug.cgi?id=941331#c6
--- Comment #6 from Bruno Friedmann ---
Petr I'm getting some difficulties to understand what would represent
/etc/apache2${instance_suffix}/httpd.conf
you mean we will move /etc/apache2 to something else ?
or the default will be empty and then /etc/apache2 will be used.
If the proposed solution look nice, I'm a bit afraid about what user (ok not
the smartest) can put in instance_suffix, and also how to handle update/upgrade
process for default files.
I'm thinking about all the wired case (like any kind of strange languages like
asian char, or more simply space etc ...)
It will become really hard to be sure on update/upgrade the packaging doesn't
create some mess.
Imagine you have in the default instance a default file with certain
instructions (Like the changes with Require versus Allow between 2.2 and 2.4)
If a user create several instances, then we increase the risk or no restart of
apache after an upgrade, until the user fix all conf files in the whole bunch
of instance.
So I'm actually in a 50% good, 50% bad feeling. I personnally believe that the
most KISS approach should be kept, but I can't find the "best" solution. I'm
just sharing some points that I know they will hurt me :-)
--
You are receiving this mail because:
You are on the CC list for the bug.
