On 20-12-2022 08:32, David C. Rankin wrote:
On 12/16/22 15:46, Andreas Radke wrote:
I suggest to fix this lack of init choice/alternative. I'd like to
implement it into the official Arch Linux repos allowing to choose
some different init replacement. We can either just add a 2nd init
system in the most simple way or allow real init-freedom[3] offering
full choice and leave it up to be further filled by the community.
I remember the discussions well. Most of which took place on the
arch-general list at the time. It may be helpful to take feedback from
the arch-general list, at least to get feedback on the current
community thoughts on the matter.
For me, I think it is a great idea Andreas. While for desktop use
systemd has captured a majority of the distros -- and no complaints,
the take-it-or-leave-it if you want Arch seems a bit restrictive.
While the change from init-scripts to systemd was uncomfortable at the
time, the transition was done well.
That said, the point made about providing an alternative init to help
with implementation on new architectures is well-taken. While systemd
does provide a great deal of functionality, it also fairly heavy.
Keeping systemd as a default while providing an alternative init for
those that would benefit from -- or just like to use -- an alternative
init sounds like a solid way to go. Essentially giving Arch the best
of both worlds.
I would like that very much and hope Connor Behan' proposal (copied
below from arch-dev-public) makes it .
Lone_Wolf
So let me make a concrete proposal.
1. Put openrc in [community] which I have used on my laptop for two
years without issue.
2. Make it depend on systemd (so it is clear we are not packaging eudev)
and make installation print a warning that users of netctl and devtools
will need to find alternatives.
3. Put openrc-arch-services in [community] as well,
4. Bugs for these two packages will be assigned to one of the three
people who've expressed interest (Andreas, TJ and myself).
