From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: RFC: avahi-stub possible?
Date: Sat, 30 May 2020 04:31:44 +0200 [thread overview]
Message-ID: <20200530023144.bgeoLQ5rSSzM5N_YGqwWOnaq8Z9KjDjk0bw2lwOaQoI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22389@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 528 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/22389#issuecomment-636263242
Comment:
PR #22406 returns to the earlier split behavior that I undid with the first 0.8 update. The original split template mentioned a desire to avoid gtk3 and gobject dependencies creeping into the base libs, but I overlooked the underlying build-cycle issue.
While the split doesn't help people install dependents without pulling in avahi libs, it at least eliminates the cycle problem.
next prev parent reply other threads:[~2020-05-30 2:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 20:20 [ISSUE] " pullmoll
2020-05-28 23:19 ` Chocimier
2020-05-28 23:46 ` ericonr
2020-05-29 9:27 ` pullmoll
2020-05-29 9:47 ` Chocimier
2020-05-29 10:13 ` pullmoll
2020-05-29 12:08 ` Johnnynator
2020-05-30 2:31 ` ahesford [this message]
2020-05-31 15:39 ` [ISSUE] [CLOSED] " pullmoll
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=20200530023144.bgeoLQ5rSSzM5N_YGqwWOnaq8Z9KjDjk0bw2lwOaQoI@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).