From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: kde5-baseapps is not installable
Date: Sun, 19 Jul 2020 01:38:20 +0200 [thread overview]
Message-ID: <20200718233820.uyg3QQbPAoA1Isgpwzldc3uIFzchmKUKg54XB7iteiI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23622@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 730 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/23622#issuecomment-660557832
Comment:
> While here, I have naive question raising since some time: why do we need common/shlibs at all, rather than 04-generate-runtime-deps querying xbps index for which installed package provides library?
It records the minimum version that provides the SONAME, which makes it easier to downgrade and partially update things.
If you start to use xbps-query to get the current version of a package providing the SONAME in the repository you end up with X packages having N different minimum version requirements just based on when they've been build and not what is actually compatible.
next prev parent reply other threads:[~2020-07-18 23:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 18:41 [ISSUE] " ericonr
2020-07-17 18:56 ` abenson
2020-07-17 18:58 ` abenson
2020-07-17 19:03 ` ericonr
2020-07-17 19:07 ` Johnnynator
2020-07-17 19:10 ` ericonr
2020-07-17 19:32 ` martindamianfernandez
2020-07-17 19:33 ` martindamianfernandez
2020-07-17 20:28 ` ericonr
2020-07-17 20:39 ` Duncaen
2020-07-17 20:41 ` ericonr
2020-07-17 22:50 ` Chocimier
2020-07-18 23:35 ` Duncaen
2020-07-18 23:36 ` Duncaen
2020-07-18 23:38 ` Duncaen [this message]
2020-07-20 18:55 ` ericonr
2020-07-21 19:58 ` Chocimier
2020-09-29 21:45 ` ericonr
2020-09-29 21:45 ` [ISSUE] [CLOSED] " ericonr
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=20200718233820.uyg3QQbPAoA1Isgpwzldc3uIFzchmKUKg54XB7iteiI@z \
--to=duncaen@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).