AW: Debian/Ubuntu: Why was the service renamed from bind9 to named?
klaus.darilion at nic.at
Wed Apr 15 07:42:46 UTC 2020
> -----Ursprüngliche Nachricht-----
> Von: bind-users <bind-users-bounces at lists.isc.org> Im Auftrag von Reindl
> Gesendet: Mittwoch, 15. April 2020 09:17
> An: bind-users at lists.isc.org
> Betreff: Re: Debian/Ubuntu: Why was the service renamed from bind9 to
> Am 15.04.20 um 09:09 schrieb Klaus Darilion:
> >>> It would be great if you undo this change before release of 18.04
> >> you confuse the upstream project with your distribution
> >> bind9 was completly wrong in the debian world as well as apache2 for
> >> httpd, on sane distributions it's "httpt" and "named" all the years
> >> beause it's nonsense to throw vesions in service names
> > I do not complain about the version number, but of the name.
> > And in my opinion it is not sane to call a service/package httpd if the name
> of the software is Apache
> and what do you do after httpd-3.0 is out?
> you won't have httpd2 and httpd3 on the same system from your
Why not? With postgresql it is very common. You have postgresql-X and a meta package pointing to the newest version. That's propapbly not what "every distribution" does, but how a good distribution like Debian and Ubuntu does it.
It is very very sane to have the version number in the package, and a package without version number pointing to the newest version. Eg. this is how the Linux kernel is handled in Debian/Ubuntu.
What about python? Only a single python interpreter is allowed with your good distros? In Debian you have all oft hem installed at the same time - this is a very very good approach!
But as you have missed again - I do not complain about the version number, but that a "winning team" was changed without seeing a problem.
More information about the bind-users