On Wed, 28 Jun 2023 at 17:20, Ansgar <ans...@43-1.org> wrote: > > Hi Simon, > > On Thu, 2023-06-29 at 00:32 +0900, Simon Richter wrote: > > According to Policy as currently published, systemd units are > > encouraged, and init scripts are mandatory. > > Please stop lying: > > +--- > | Packages that include system services should include systemd service > | units to start or stop those services. [...] > | > | If the package does not include a service unit (if, for example, no > | one has yet written one), including an init script, as described > | below, to start the service is encouraged. > | > | Packages including a service unit may optionally include an init > | script to support other init systems. > +---[ Policy 9.3.1 ] > > And no, this isn't exactly new. Except apparently for you. > > The real exhausting thing is people lying, FUD, spreading conspiracy > theories (ominous commercial sponsors (Rothschilds? Soros?)), endless > revisiting of decisions (should we prepare to revert usrmerge because > the attention of ominous commercial sponsors might shift elsewhere?), > claiming systemd is rot/cancer/an infection/the Windows registry and so > on. > > I agree that this isn't a technical issue though. > > > > That's the thing: few people want init scripts. I don't want init > > scripts either. > > This very thread only exists because people want init scripts. I agree > that this is very few people though. > > > What I want is an init system that can be maintained inside a community > > project like Debian without burning out people and endangering the long > > term viability of the project. > > And claiming this isn't possible with systemd is one thing: FUD. > > > That is where systemd fails us as a community project, because the > > environment in which most of development is happening is not > > hospitable to community building efforts, and the complexity of the > > project constitutes a high barrier to entry, which acts as a further > > selection filter for contributors. > > More FUD.
Let's look at some community numbers for two init system projects in question, we like to look at hard data after all, don't we. To spicy it up, without mentioning which is which: $ git shortlog -s | cut -c8- | wc -l 2318 $ git shortlog -s | cut -c8- | wc -l 7 Just from this alone, it certainly seems true that one of those is a project that "fails as a community project" and that is "not hospitable to community building efforts". Anyone want to guess which is which? Kind regards, Luca Boccassi
