Hacker News Reader

frodob12on Devuan Jessie 1.0.0 stable release (LTS)

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832508

Last i looked no-one wanted to maintain the shim, upstream looked dead, but things may have changed.

frodob12on Devuan Jessie 1.0.0 stable release

Another is that they can see where the systemd bus is going and it's not somewhere they choose to follow.

frodob12on Devuan Jessie 1.0.0 stable release

But these are hard deps not just recommends so will pull in systemd dependencies regardless of it using them or not. If it were a recomends type dep, again no one would have a problem. It used to be considered bad packaging to hard dep when recommends or suggests would suffice.

7.2 states: "When selecting which level of dependency to use you should consider how important the depended-on package is to the functionality of the one declaring the dependency"

You say "being able to use software under another init system." Looks like the level of dependency should be adjusted to fit your point.

frodob12on Devuan Jessie 1.0.0 stable release

They were told to by debian. They argued for as long as they could while debian was still 'their' distribution to change the direction systemd would take it. It was clean that wasn't going to happen. Final response; "If you don't like it you can always fork. But you'll never release anything."

So now they have forked and they have released. So now their splitters. Cake and eat it types, what can you do?

frodob12on Devuan Jessie 1.0.0 stable release

That is the main complaint.