Consider dropping libdaemon

[rossburton]

Considering libdaemon is dead upstream and pretty small, maybe avahi should just copy/paste that code instead?

[lathiat]

Are projects generally using some kind of library for the equivalent functionality? Or just doing DIY.

We could possibly also drop a bunch of it in favour of systemd functionality, though, may accidentally alienate the alternative distributions and BSDs, etc.

[rossburton]

On 23 May 2018 at 02:29, Trent Lloyd notifications@github.com wrote:

Are projects generally using some kind of library for the equivalent functionality? Or just doing DIY.

We could possibly also drop a bunch of it in favour of systemd functionality, though, may accidentally alienate the alternative distributions and BSDs, etc.

Across Debian:

$ apt-cache rdepends libdaemon0 libdaemon0 Reverse Depends: libdaemon-dev shairport-sync shairport-sync mpdcron libteam-utils infinoted libdaemon0-dbg avahi-dnsconfd ifplugd avahi-autoipd avahi-daemon

It appears most people are just DIY. I would support the use of systemd as an alternative but a hard requirement on libsystemd would be sad as we do still have non-systemd users.

Ross

[midicase]

Dead or just that it hasn't needed any improvements for years? "Version 0.14 is feature complete."

I use libdaemon for client projects since it has some nice features, but avahi doesn't need or use. DIY is only a handful of lines.

No systemd. avahi is widely used on embedded systems where I suspect will resist systemd for a really long time.

[rossburton]

The libdaemon git repository has been unavailable for years, so let's hope that libdaemon is perfect. That counts as dead in my book.

Ross

On 23 May 2018 at 11:34, midicase notifications@github.com wrote:

Dead or just that it hasn't needed any improvements for years? "Version 0.14 is feature complete."

I use libdaemon for client projects since it has some nice features, but avahi doesn't need or use. DIY is only a handful of lines.

No systemd. avahi is widely used on embedded systems where I suspect will resist systemd for a really long time.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/lathiat/avahi/issues/182#issuecomment-391300823, or mute the thread https://github.com/notifications/unsubscribe-auth/AAB-ik4vePYp7iDsyY3WMVTc1vWsOLMVks5t1TsYgaJpZM4UJQqd .

[midicase]

http://git.0pointer.net/libdaemon.git/

It's just the libdaemon webpage is out of date.

[rossburton]

Someone really should pick it up, push it to github, actually roll a 0.15 with the license change, and make it look alive again...

On 23 May 2018 at 11:39, midicase notifications@github.com wrote:

http://git.0pointer.net/libdaemon.git/

It's just the libdaemon webpage is out of date.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/lathiat/avahi/issues/182#issuecomment-391302138, or mute the thread https://github.com/notifications/unsubscribe-auth/AAB-inHauqNjmJMsdOKdz3zzqeWeI27iks5t1TxhgaJpZM4UJQqd .

[nanonyme]

A project that cannot roll releases is effectively dead. Hacking on master branch doesn't mean much. I would also note majority of newer releases were tagged by Lennart Poettering who created systemd.

[nanonyme]

Also entire 0pointer.net is Lennart Poettering's site.

[evverx]

It isn't the only abandoned dependency unfortunately (https://github.com/avahi/avahi/issues/527) and it would be great not to depend on it of course. That being said in places where those things matter the library is unlikely to be pulled from that repository directly because it was probably copied/forked and checksums/signatures were added on top to avoid relying on personal git repositories that can go down, be popped or whatever.