1 |
On Wed, May 8, 2013 at 1:18 PM, Michael Mol <mikemol@×××××.com> wrote: |
2 |
> It would effectively need to be bumped every time any package added, |
3 |
> removed or changed a unit file requirement. Also every time a unit |
4 |
> file-bearing package is added or removed from tree. |
5 |
> |
6 |
> That would be one insanely hot package. |
7 |
|
8 |
Splitting out unit files might have made sense when systemd was a |
9 |
highly experimental piece of software that a few people are tinkering |
10 |
with. It is rapidly becoming the most commonly used init.d-like |
11 |
implementation out there (mainly by virtue of the fact that every |
12 |
other one tends to be used by a single distro). Quite a few are using |
13 |
it on Gentoo. |
14 |
|
15 |
I think it really needs to be accommodated in the same way as openrc |
16 |
init.d scripts. I'm not saying that maintainers should be required to |
17 |
create them if they're missing (they don't even have to do that for |
18 |
openrc init.d scripts). However, if users or other devs contribute |
19 |
them and vouch that they work, then they should be included in |
20 |
packages. |
21 |
|
22 |
This really isn't any difference from the myriad of unusual |
23 |
configurations that Gentoo supports. If somebody on the Prefix team |
24 |
suggests some changes to my ebuild to make it more Prefix-friendly I |
25 |
collaborate with them. I don't need to get Prefix working on a sparc |
26 |
to accept their input that some change to the ebuild makes life easier |
27 |
on this arch. Sure, I'll make sure we're not adding regressions, but |
28 |
this is a community effort. The same is true if I get a bug that some |
29 |
package I maintain has some problem on hardware I don't own (like a |
30 |
different graphics card). I can't test it, but I can work with what |
31 |
I'm given and call for testing and so on. |
32 |
|
33 |
Bottom line is that none of this should really be inconveniencing |
34 |
maintainers much - nobody is required to create unit files. However, |
35 |
if a friendly user submits a bug with one attached, then the |
36 |
maintainer should strongly consider adding them to the package at the |
37 |
next convenient time. |
38 |
|
39 |
Nobody has to use systemd if they don't want to, but honestly, it |
40 |
seems like it is slowly taking over. It sounds like OpenRC will |
41 |
support compatible unit files, and that is really a win-win all around |
42 |
as it means that users of both platforms will benefit from work |
43 |
invested on the other. That will mean that those who want to stick |
44 |
with OpenRC/Eudev/whatever will have a good experience even if many |
45 |
devs abandon those platforms, and vice-versa. |
46 |
|
47 |
Rich |