Fedora To Finish Phasing Out System V Init Scripts
Fedora will be finishing up their System V to systemd unit migration in the months ahead.
When Fedora 24 is branched from Rawhide in February, any packages still relying upon System V init scripts rather than systemd unit files will be retired. Packagers who maintain packages still needing sysVinit scripts need to apply for delays now if you can't migrate off System V before February.
While Fedora 25 isn't scheduled to have any packages with System V init scripts (unless delays are approved), Fedora doesn't plan to remove System V compatibility from Fedora in order to maintain support for legacy, third-party software.
More details on this final push for System V to systemd unit migration for Fedora packages can be found via this devel list message. While Fedora has been pushing systemd for a while and most open-source software out there now has systemd unit files where needed, per this message, there still appears to be a number of affected packages still with System V init scripts.
When Fedora 24 is branched from Rawhide in February, any packages still relying upon System V init scripts rather than systemd unit files will be retired. Packagers who maintain packages still needing sysVinit scripts need to apply for delays now if you can't migrate off System V before February.
While Fedora 25 isn't scheduled to have any packages with System V init scripts (unless delays are approved), Fedora doesn't plan to remove System V compatibility from Fedora in order to maintain support for legacy, third-party software.
More details on this final push for System V to systemd unit migration for Fedora packages can be found via this devel list message. While Fedora has been pushing systemd for a while and most open-source software out there now has systemd unit files where needed, per this message, there still appears to be a number of affected packages still with System V init scripts.
8 Comments