I open this issue to share a common best practices to follow in the new ebuild about `systemd` use flag support and ebuild integration.

As you know in the Macaroni project is present a release that will be used to experiment solution that will supply a solution similar to Systemd (now for starting it uses Systemd).

On building the packages i see that a lot of ebuild are only openrc orientend.
I think that is important supply a clear idea about what is a best practices to follow for dev users that generate and update ebuilds.

I good start point could be this maybe:

• if the original package contains .service is better define a `systemd` use flag that will install that files if the use flag is enable and that will skipped systemd stuff if not.

The current status is that:
a) there are packages that install systemd files on funtoo rootfs with openrc always
b) related to the point a in this ebuild is not present a `systemd` use flag that permit to skip these files
c) there are packages with systemd use flags but systemd is not usable and this requires the following patches to have systemd in funtoo: https://github.com/funtoo/macaroni-funtoo/tree/systemd/packages/seeds/funtoo-kits/kits-patches/core-kit

Just to clarify to Funtoo users that the mission of this issue is not begin to integrate Systemd in funtoo but define a good base to:

• help me on the work with macaroni-systemd release that will be used to integrate a systemd replacer more funtoo users friendly
• prepare a constructive comparison table of the existing technologies to identify the pro/cons that will be the base for the requirements of the new tool
• the idea of the new tool will be to support the same systemd format .service to simplify the integration of the new tool.

For all packages available in Macaroni i could create a report automatically of the packages with systemd files not needed.