On Tue, May 03, 2016 at 08:50:33AM -0400, Jacob Stiffler wrote: > Hello, > > With systemd recently enabled, I a wondering how to resolve when a > package supports both systemd and sysvinit, but does not provide > service files for every initscript it provides. > > I am looking into busybox. It only provides systemd service files > for syslog, but provides initscripts for other services such as > udhcpd. By enabling the systemd distro feature and removing the > sysvinit feature, all initscipts are removed from the installation, > and thus services without systemd service files become unsupported. > > Is there any way to resolve this without creating a udhcpd service > file? Should sysvinit also be a DISTRO_FEATURE while the transistion > to systemd is in progress?
Yeah, I was overzealous when disabling sysvinit from the DISTRO_FEATURES Not all packages provide native systemd unit/service files and getting a pure systemd-only build would require some extra work. It is expected to use some of the old initscripts with systemd as a fallback, hence both DISTRO_FEATURES are still needed. -- Denys _______________________________________________ meta-arago mailing list [email protected] http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
