test_epsilon
Joined 5 years ago
Joined 5 years ago
They are used to make packages with differently named binaries able to implement standard shell commands.
There is no need to match binary names. It doesn't really help with anything.
But seriously (and I can't see linkedin), it sounds like the qualification is most relevant in response to the comment the OP made.
And it's entirely possible to use different software names for projects that implement a compatible API or service, the claim that it's for compatibility is pretty bogus. It's not "standard", especially not for an adversarial fork. And that's not why the alternatives system exists, the alternatives system exists so differently named packages can implement a particular service (i.e., exactly the opposite, for the equivalent in shell commands). So that's underhanded.
However creating a fork with the same acronym and name for the daemon or binaries or whatever seems pretty under-handed.
Was a release announcement for the original software moderated, on a list where release announcements had been posted without moderation before the fork? Was the author banned from lists?
Very few any countries are.
That wasn't the important part of the response to your post though, the important part is that it wasn't stolen or conquered.
You're okay if the government privatizes certain "problematic" services it provides and allows the now private organization to violate peoples' rights?
They are by definition.