But the premise "you can just maintain your own non-systemd distribution on OBS" is IMO a plain lie,
Well, other than the necessary build power I am not aware of any limitation in this area. Please fell free to educate me.
Based on the experience I have with OBS there is nothing in the way for me to set up a subproject in my HOME and build all of openSUSE, create iso images from it etc. I can maintain patches that add sysV init support in the project and do whatever. There may of course be issues that I am not aware of as I have never attempted anything at that scale. Again, please share your knowledge.
Proclaiming that statements are "lies" is not very constructive.
True. For this purpose, the obs project Base:sysv was created. Please have a look at the project's description: It states that there should be a meta-package (at some point in time in the future) that, if selected, pulls in everything else from the repo and thereby obsoletes systemd and installs glue packages that are needed. A system like this would easily follow my (personal?) demand for * separation of boot (and after boot) glue pieces according to their respective purposes * leaving subsystems up to their own businesses (cgroups, network, device naming, ...) * leaving services on their own (0,1,2 on /dev/null, chdir("/"), fork() and maybe setsid(2)) ) * configuration of the framework not dependent on a semi-programming language where changes to configuration have unforseeable consequences. * a reasonable network device naming scheme. This is ridiculous. I haven't had enough time to dig into this yet, so it's pretty much vanilla yet. With changing circumstances in October/November this could change. If you want to participate, feel free. Also please let me know if you wish to be included in the prioject.
Later, Robert
Thanks, Roman. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org