From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: SDL2-devel polutes masterdir with tenths of devel packages.
Date: Fri, 29 Oct 2021 20:24:00 +0200 [thread overview]
Message-ID: <20211029182400.0entkrop-It3zKV-L1heYqhzGyq4kiykLQhv3rP6WkI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33796@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/33796#issuecomment-954957791
Comment:
> if a package like SDK gets fixed to list correct dependencies in future, this will prolly cause issue for a lot of packages using it in tree, if underspecified. And prolly there are a lot of those.
If someone removes most of the deps, it's expected of them to test dependants and make sure things are still being picked up. The libraries needed for static linking should be in the `-devel` package as well, even if most of our packages don't make that usage.
> I dont know the structure of void builder chroot well yet, but this also may increase build time by a significant factor,
`./xbps-src fetch SDL2_image` took 20s, including fetching the 11MB distfile and repository indexes, actual unpacking took a few seconds.
Unless you're volunteering to do the work of checking that all of packages are indeed necessary for static linking and that other packages aren't specifying fewer dependencies than they need to, I'd like to close this issue.
next prev parent reply other threads:[~2021-10-29 18:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 19:32 [ISSUE] " VoidPorts
2021-10-28 21:52 ` paper42
2021-10-29 15:32 ` VoidPorts
2021-10-29 15:37 ` VoidPorts
2021-10-29 15:39 ` VoidPorts
2021-10-29 15:40 ` Chocimier
2021-10-29 18:24 ` ericonr [this message]
2021-10-30 6:21 ` [ISSUE] [CLOSED] " VoidPorts
2021-10-30 6:21 ` VoidPorts
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=20211029182400.0entkrop-It3zKV-L1heYqhzGyq4kiykLQhv3rP6WkI@z \
--to=ericonr@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).