(mentioning here since I won't be in the meeting)

+1 to the general feature here. I'd like to add a requirement that settings are migrated as best as possible on upgrade, as this is biting people on F16 upgrades.

Replying to [comment:1 notting]:

(mentioning here since I won't be in the meeting)

+1 to the general feature here. I'd like to add a requirement that settings are migrated as best as possible on upgrade, as this is biting people on F16 upgrades.

I think it wont be a problem for F15 and onwards since we have switched to systemd if i'm not mistaken the whole users chkconfig on/off and the need to reset the service status upon upgrade should be out of the picture.

Anyway we already are trying to do our best here in somecases it cant be helped ( like freeipa ) in other it can be ( like autofs which was a set of mistakes ) allthou this particular snipped from fpc is working against it.

"Unit files should be named after the software implementation that they support as opposed to the generic type of software. So, a good name would be apache-httpd.service and bad names would be httpd.service or apache.service as there are multiple httpd implementations and multiple projects produced by the apache foundation."

for instance if we would rename the unit file in question here ( httpd.service ) it would break backwards compatibility with the service command.

Just my 2 cents...

This feature was approved at the 2011-11-14 meeting.

We would like to re-iterate that provenpackagers are welcome to commit changes for this feature.