No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
... I still need release notes in the release notes section :) --[[User:Rbergero|Rbergero]] 18:05, 12 December 2011 (UTC) | ... I still need release notes in the release notes section :) --[[User:Rbergero|Rbergero]] 18:05, 12 December 2011 (UTC) | ||
I can't see why Fedora would want a presets feature that works for 5% of the packages. Support in systemd can obviously go in any time, but when the packaging guidelines change, all existing scriptlets need to be converted within a single release (... and this probably means finding some provenpackagers willing to do ~50% of the work). -- [[User:Mitr|Mitr]] 16:21, 16 December 2011 (UTC) | |||
Putting the presets into fedora-release creates centralizes information that really doesn't need to be centralized and adds another bottleneck. I think it would make more sense for Fedora if (systemctl preset FOO.service) checked the presets, and defaulted to state described somewhere ''inside the PRM package'' (presumably in the unit file) - so that the default preset configuration could be ''empty''. -- [[User:Mitr|Mitr]] 16:21, 16 December 2011 (UTC) | |||
I think the macros need to be approved by the FPC (obviously), and they should probably be discussed with RPM developers (they are working on a different mechanism for common scriptlets, and doing the migration twice is just unnecessary work). -- [[User:Mitr|Mitr]] 16:21, 16 December 2011 (UTC) | |||
As a minor comment, from a semantics point of view, it's not always quite clear what is the "Fedora default" - e.g. when I enable NTP in firstboot, and it runs (systemctl enable chronyd.service), is the "Fedora default" off or on? -- [[User:Mitr|Mitr]] 16:21, 16 December 2011 (UTC) | |||
Revision as of 16:21, 16 December 2011
Please add release notes to the release notes section so that this may be sent to fesco. I disagree that there is not a need to mention; there is plenty of information in the Benefit to Fedora section that would be useful in release notes, and would ensure that the feature would actually be known about and get used by community members within Fedora, at the bare minimum.--Rbergero 13:06, 14 November 2011 (UTC)
... I still need release notes in the release notes section :) --Rbergero 18:05, 12 December 2011 (UTC)
I can't see why Fedora would want a presets feature that works for 5% of the packages. Support in systemd can obviously go in any time, but when the packaging guidelines change, all existing scriptlets need to be converted within a single release (... and this probably means finding some provenpackagers willing to do ~50% of the work). -- Mitr 16:21, 16 December 2011 (UTC)
Putting the presets into fedora-release creates centralizes information that really doesn't need to be centralized and adds another bottleneck. I think it would make more sense for Fedora if (systemctl preset FOO.service) checked the presets, and defaulted to state described somewhere inside the PRM package (presumably in the unit file) - so that the default preset configuration could be empty. -- Mitr 16:21, 16 December 2011 (UTC)
I think the macros need to be approved by the FPC (obviously), and they should probably be discussed with RPM developers (they are working on a different mechanism for common scriptlets, and doing the migration twice is just unnecessary work). -- Mitr 16:21, 16 December 2011 (UTC)
As a minor comment, from a semantics point of view, it's not always quite clear what is the "Fedora default" - e.g. when I enable NTP in firstboot, and it runs (systemctl enable chronyd.service), is the "Fedora default" off or on? -- Mitr 16:21, 16 December 2011 (UTC)