From: Piraty <Piraty@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: Update avahi, take ownership
Date: Thu, 14 May 2020 15:06:10 +0200 [thread overview]
Message-ID: <20200514130610.zhgzUwQrNBid-3d0c9nSxI2ExHj9tHH5q8CbujeuURg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21731@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]
There's a merged pull request on the void-packages repository
Update avahi, take ownership
https://github.com/void-linux/void-packages/pull/21731
Description:
This brings avahi and its subpackages up to date. Included are new libraries to incorporate avahi with libevent or qt5, as new subpackages. Also, the Python parts of avahi are compatible with py3, so there are new `-python3` subpackages as appropriate. The `avahi-python` package is still usable with py2 and has been preserved; `avahi-python-utils` is now an empty meta to bring in the new `avahi-python3-utils`, as the contents of the newer package supplant the older.
EDIT: I've also unified the `avahi-discover` and `avahi` templates. They were separate to avoid dependencies like `gtk+3` in the base packages. However, I've double-checked the dependencies when building all of the subpackages from one template, and these extra dependencies do not leak into the base package. The unification makes maintenance easier and saves build time, because now `avahi-discover` and its subpackages can just copy files from the `avahi` build rather than rebuilding everything (with the potential for mismatched build options) a second time just to extract the UI bits.
next prev parent reply other threads:[~2020-05-14 13:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 20:53 [PR PATCH] " ahesford
2020-05-09 16:35 ` [PR PATCH] [Updated] " ahesford
2020-05-09 16:40 ` ahesford
2020-05-09 21:14 ` ahesford
2020-05-11 18:19 ` ahesford
2020-05-14 12:49 ` ahesford
2020-05-14 13:06 ` Piraty [this message]
2020-05-29 12:09 ` Johnnynator
2020-05-29 14:46 ` ahesford
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=20200514130610.zhgzUwQrNBid-3d0c9nSxI2ExHj9tHH5q8CbujeuURg@z \
--to=piraty@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).