Quoting Simon Hobson (simon@???):

> So when someone states that "it's just a library, it doesn't do
> anything" then that needs taking with a pinch of salt because once
> anything calls one of it's functions, then that library can do lots of
> stuff.

On the other hand, when the person says 'it's just a library; it doesn't
do anything'[1], _and_ accompanies that with the crucial detail that the
reason this _particular_ library doesn't do anything is that it's merely
interface code to something else you have deliberately left out, _and_
went to the trouble of explaining that a library can do anything except
be directly invoked as an executable, _and_ scrupulously referred you to
good documentation on libraries so you can learn what they are if you
honestly do system administration but don't know what a library is ---
then maybe you should keep the salt in its box, because you never know
when you might need salt for something other than failing to understand
information in context.

> So the point I've been making before is that, even if libsystemd0
> "does nothing" now, we can't be complacent that it won't change.

And package maintainers are evil corrupt collaborators who wouldn't
catch this and reject the change, and the entire Linux community would
be incompetent to notice and take remedial action.

Of course! How did I miss that?

> OK, this many be paranoia

No, really?


[1] That person endeavours to not write run-on sentences, so would in
fact use a semicolon rather than a comma.