1 |
Ok |
2 |
|
3 |
So I'm reading about systemd support in ebuilds; just trying to |
4 |
understand the beast wee bit better. |
5 |
|
6 |
In in this ebuild: www-misc/monitorix (A lightweight system monitoring tool)f |
7 |
|
8 |
the newest version has added this line to the ebuild: |
9 |
|
10 |
"systemd_dounit docs/${PN}.service" |
11 |
|
12 |
|
13 |
Looking that the systemd.eclass, all I see is: |
14 |
"systemd_dounit <unit>... |
15 |
Install systemd unit(s). Uses doins, thus it is fatal in EAPI 4 and |
16 |
non-fatal in earlier EAPIs. " |
17 |
|
18 |
Which seems reasonable, but tells me nothing what the line does. I can |
19 |
speculate that monitorix becomes a registered process, if you are |
20 |
running systemd, but is otherwise ignored on a openrc based system? |
21 |
|
22 |
It would seem to me the devmanual needs some more "prose" so on can |
23 |
discern what the systemd.eclass is doing. And yea, I'm off to look |
24 |
at the code for systemd.eclass as I'm sure it's clear as mud..... |
25 |
|
26 |
The trouble is I find this code everywhere with google. So where |
27 |
is the best place to read the current systemd.eclass code and where |
28 |
do I look at the 9999 stuffage; ?should? I become curious about that |
29 |
eclass or other eclass codes.....? |
30 |
|
31 |
guidance and insight is appreciated. |
32 |
|
33 |
|
34 |
James |
35 |
|
36 |
|
37 |
|
38 |
|
39 |
|
40 |
James |