On Feb 18, 2015 11:12 PM, "James" <[email protected]> wrote:
>
> Ok
>
> So I'm reading about systemd support in ebuilds; just trying to
> understand the beast wee bit better.
>
> In in this ebuild: www-misc/monitorix (A lightweight system monitoring
tool)f
>
> the newest version has added this line to the ebuild:
>
> "systemd_dounit docs/${PN}.service"
>
>
> Looking that the systemd.eclass, all I see is:
> "systemd_dounit <unit>...
> Install systemd unit(s). Uses doins, thus it is fatal in EAPI 4 and
> non-fatal in earlier EAPIs. "
>
> Which seems reasonable, but tells me nothing what the line does. I can
> speculate that monitorix becomes a registered process, if you are
> running systemd, but is otherwise ignored on a openrc based system?
>
systemd_dounit copies a service file to ${ED}/usr/lib/systemd/system.
Nothing more.
You would need some understanding of how systemd works to know what that
actually means for an end user. A service unit serves basically the same
purpose as an init script. They are ignored if you do not boot with
systemd.
> It would seem to me the devmanual needs some more "prose" so on can
> discern what the systemd.eclass is doing. And yea, I'm off to look
> at the code for systemd.eclass as I'm sure it's clear as mud.....
>
> The trouble is I find this code everywhere with google. So where
> is the best place to read the current systemd.eclass code and where
> do I look at the 9999 stuffage; ?should? I become curious about that
> eclass or other eclass codes.....?
The eclasses are all in /usr/portage/eclass.
