All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: fontaine.fabrice@gmail.com,
	Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [git commit] package/avahi: fix libavahi-client handling
Date: Sat, 13 Jan 2024 20:56:29 +0100	[thread overview]
Message-ID: <877ckdt3bm.fsf@48ers.dk> (raw)
In-Reply-To: <20240113184532.3d393158@windsurf> (Thomas Petazzoni's message of "Sat, 13 Jan 2024 18:45:32 +0100")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:

 > Hello Peter,
 > On Sat, 13 Jan 2024 08:52:20 +0100
 > Peter Korsgaard <peter@korsgaard.com> wrote:

 >> Does this change really make sense in the context of Buildroot? Libavahi
 >> is a library to talk to the avahi daemon, so not very useful without the
 >> daemon.

 > True. To be honest, I didn't put too much thinking when applying
 > Fabrice's patch: the daemon was not strictly needed when building the
 > library, dropping the dependency made sense, so I applied. If there is
 > a runtime dependency on the daemon, then indeed maybe we should keep
 > the dependency. No strong feeling about it, and I certainly wouldn't
 > feel offended if the commit was reverted.

It is at least my understanding that libavahi doesn't make much sense
without the daemon, unless I am missing something. Fabrice?

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-01-13 19:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-06  9:51 [Buildroot] [git commit] package/avahi: fix libavahi-client handling Thomas Petazzoni via buildroot
2024-01-13  7:52 ` Peter Korsgaard
2024-01-13 17:45   ` Thomas Petazzoni via buildroot
2024-01-13 19:56     ` Peter Korsgaard [this message]
2024-01-14 12:40       ` Fabrice Fontaine

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877ckdt3bm.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.