Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=505360 --- Comment #15 from Patrick Monnerat <pm@xxxxxxxxxxxxx> 2010-05-04 13:04:31 EDT --- Well... this is a philosophical problem that could well degenerate into a troll :-( In the case you mention, you're probably right, but this implies system updates are done while someone changes the server configuration, saves the (bad) configuration and does not test/apply the changes immediately... IMHO, this situation will occur very seldom. However, I'm not wrong because there is an /etc/httpd/conf.d/*.conf file in this package and a server reload is needed to enable/disable it. phpPgAdmin (for example) reloads the server at post time for the same reason. And by the way, this is just a reload, not a restart. This ideal situation would be to have an Apache-enabled /usr/share/js directory for those kind of packages (a bit like /usr/share/php for php packages). This would allow new js packages to get rid of a specific httpd configuration file. But Fedora does not (yet) include such a directory in its standard base, nor there is specific guidelines for javascript packaging. In the meantime, I suggest we meet halfway by reloading the server only at first package install and last uninstall. @Kevin: would it be satisfactory to you ? -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review