On Tuesday 12 March 2019 at 13:07:08, aitor_czr wrote:

> Hi,
>
> On 12/3/19 9:25, KatolaZ wrote:
> > Again, this is pretty pointless: just look for reverse-deps on libdbus
> > and you'll find the answers you are looking for.
> >
> > /var/lib/dbus/machine-id is read by anyting that opens a dbus channel
> > and/or sends/receives a message through dbus. It is not read by the
> > process itself, rather by libdbus (please have a look at dbus' code).
>
> The next systemd...

If that's a serious comment, what is evil/wrong with (lib)dbus?

I ask because I think if we can define what we specifically disagree with about
systemd and dbus (and anything else which might qualify), this would be a
powerful message to put on the Devuan web page to explain precisely why it
exists and why people should consider migrating to it.

If we can identify things other than systemd which we consider to be bad for
people (provided there's a common justification for why they're bad) I think
this is far better than just saying "we don't like systemd" as a specific
element of modern Linux distros.

> Recently i packaged wpa removing its dependency on libdbus, but i did it for
> lubuntu (merely a trial) because i was testing the live-sdk on it; so, this
> packaging is missing in the repository of gnuinos. Most of the network
> managers depend strongly on dbus, such as conman, wicd, etc.

That doesn't stop us from examining "what does it do and why do these things
need it" and deciding whether to come up with an alternative which works in a
way we approve of.

The starting point, though, is to work out "what do we not approve of in the
way this thing does its job?"


Antony.

--
Normal people think "If it ain't broke, don't fix it".
Engineers think "If it ain't broke, it doesn't have enough features yet".

                                                   Please reply to the list;
                                                         please *don't* CC me.