Update mesh announce

[AiyionPrime]

This closes #146

More details in commit messages of PR-commits;

Basically upstream implemented ffnord/mesh-announce#60 .
We pulled from their master and broke our config.
This does not happen often; I'd vote for not changing the repos upstream because of this.

[AiyionPrime]

Reviews are requested; I'll merge this today at around 18:00 as our current state is broken; and this wont break it more.

Tested on sn07:
https://hannover.freifunk.net/karte/#/en/map/88e640ba7021

[AiyionPrime]

Tested on sn01 as well.

[AiyionPrime]

Will go on with 08 later to test for stretch issues.

[1977er]

Just out of curiosity: why is the service called respondd, but the software is called mesh-announce?

[AiyionPrime]

Because mesh-announce provides the capabilities of respondd.
It's the same with your dhcp service.
Kea provides dhcpd, so the service is called dhcpd, because any sysadmin who'll come along would suffer a lot if he'd need to find out first, which dhcp server is currently used.

The pattern is furthermore neat, as it makes conflicting providing services more obvious; hence try having two programs providing the same service dhcpd or respondd.

In this provide-structure respondd or dhcpd are more or less standardized interfaces.

[1977er]

Bad example. ;) Just yesterday it took me some time to find out, that its a bad idea to go against the package mantainer. Long story short: its isc-kea-dhcp4-server again.

I see your point, but I think its more helpful/intuitive when all components (process name, config file, paths etc) of a software share the same name.

[lemoer]

LGTM. Can be merged.

[AiyionPrime]

Not a bad example, just not considered. If your PM deploys it as kea, it's kea.
But the PM for mesh-announce calls it respondd, so I won't rename this, sorry.

[1977er]

I did not want you to rename it. I was just curious. :)

[AiyionPrime]

rolled out successfully on all supernodes