From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: alsa-lib: update to 1.2.3.2.
Date: Wed, 22 Jul 2020 17:22:16 +0200 [thread overview]
Message-ID: <20200722152216.CnHdijk1S7nXNNOC9uVOmYMvM4C96K2Dsui7w4EOWNc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23713@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 962 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/23713#issuecomment-662517111
Comment:
The shlib dependency resolution in XBPS and xbps-src helps prevent a lot of problems, but that doesn't mean subtle issues can't appear when one updates a library and its headers but doesn't rebuild against the new version. Even if there are no problems, it's possible that the build objects can differ in some meaningful way when built against an older version of the library, which means versions built by xbps-src after the library is updated will be different than the official binary packages for no apparent reason.
Obviously we accept this tradeoff every time we update a library because revbumping every dependant of every library "just in case" isn't worth the cost. But if you're updating a dependent and a library within a few hours of one another, why not ensure proper ordering just to ensure consistency?
prev parent reply other threads:[~2020-07-22 15:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 10:27 [PR PATCH] " ailiop-git
2020-07-22 14:50 ` ahesford
2020-07-22 14:50 ` [PR PATCH] [Merged]: " ahesford
2020-07-22 15:02 ` ailiop-git
2020-07-22 15:22 ` ahesford [this message]
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=20200722152216.CnHdijk1S7nXNNOC9uVOmYMvM4C96K2Dsui7w4EOWNc@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).