From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: libxkbcommon: update to 1.0.1.
Date: Tue, 29 Sep 2020 16:08:21 +0200 [thread overview]
Message-ID: <20200929140821.Hn41nVJfPccM2qBZ66Cm-mxbrBPVHmSC1_xLJ7xCpX8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25134@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/25134#issuecomment-700729997
Comment:
`shlib_provides` is used to tell `xbps-src` about shared objects it doesn't automatically find, for example if a package keeps an unversioned file like `/usr/share/somelib/liblib.so` and you want to link other packages against that library. In this case, you should remove those lines.
As for `common/shlibs`, it doesn't *really* matter that libraries are included unless you want to link against them in another package. However, I'd say that, for consistency, if you have to have one of the libraries listed (which is the case here), you might as well include both. The exception is if the libraries are in some private directory like `/usr/lib/xkbcommon/libxkbregistry.so.0`, which will be picked up by `xbps-src` but are probably not intended for public consumption.
What dependants have you tested against this update? They claim API and ABI compatibility across the big version jump, but given the broad list of dependants, it would be good to do some sanity checks.
next prev parent reply other threads:[~2020-09-29 14:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-27 17:12 [PR PATCH] " dashezup
2020-09-27 18:19 ` [PR PATCH] [Updated] " dashezup
2020-09-29 14:08 ` ahesford [this message]
2020-09-29 20:59 ` dashezup
2020-09-29 21:26 ` dashezup
2020-09-29 21:55 ` dashezup
2020-09-29 21:55 ` dashezup
2020-09-29 21:56 ` [PR PATCH] [Updated] " dashezup
2020-09-29 22:12 ` dashezup
2020-09-29 22:12 ` dashezup
2020-09-29 22:42 ` dashezup
2020-09-30 1:24 ` [PR PATCH] [Updated] " ahesford
2020-09-30 1:29 ` ahesford
2020-09-30 9:48 ` dashezup
2020-09-30 12:39 ` [PR PATCH] [Closed]: " 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=20200929140821.Hn41nVJfPccM2qBZ66Cm-mxbrBPVHmSC1_xLJ7xCpX8@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).