From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: verify dependencies between subpkgs
Date: Wed, 16 Aug 2023 18:21:19 +0200 [thread overview]
Message-ID: <20230816162119._9-G7xVpBVr7S2PhrrzBqO2aqAUCYdvrZ1VEHBY39zQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45504@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 480 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/pull/45504#issuecomment-1680910904
Comment:
This seems like a good idea.
There is also the case where we add `libGLESv2.so discord-0.0.7_1` for a bunch of nonfree packages in `common/shlibs`.
This seems somewhat related since some non-free packages either do this or use `noverifyrdeps=yes`. Does this also solve this issue or is it possible to also solve that with this PR?
next prev parent reply other threads:[~2023-08-16 16:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 12:58 [PR PATCH] " sgn
2023-08-16 13:05 ` [PR PATCH] [Updated] " sgn
2023-08-16 16:21 ` Duncaen [this message]
2023-08-17 0:08 ` sgn
2023-08-17 0:15 ` sgn
2023-08-17 4:42 ` [PR PATCH] [Updated] " sgn
2023-08-17 11:34 ` sgn
2023-08-29 6:18 ` sgn
2023-08-29 15:17 ` sgn
2023-08-30 6:24 ` [PR PATCH] [Merged]: " sgn
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=20230816162119._9-G7xVpBVr7S2PhrrzBqO2aqAUCYdvrZ1VEHBY39zQ@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).