From: pullmoll <pullmoll@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] MuseScore pulls whole clang as an indirect dependency
Date: Sun, 20 Sep 2020 01:22:54 +0200 [thread overview]
Message-ID: <20200919232254.QR2UIdZdjD26QjpihHrd2HnZewMwknsmZ1fFiMosSUI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-6949@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1465 bytes --]
Closed issue by laserbat on void-packages repository
https://github.com/void-linux/void-packages/issues/6949
Description:
### System
* xuname:
*xuname: Void 4.20.1_1 x86_64 AuthenticAMD uptodate rrrmFFFFFFFF*
* package:
*musescore-3.0_1*
*qt5-tools-5.11.3_3*
I'm not sure if this issue will be taken seriously, but it seems pretty bizarre for me, especially since void is positioned as minimalist linux distro.
As far as I can understand the issue, clang should be optional dependency of qt5-tools, like it is in arch linux, since it's a very big package and is unnecessary for most functionality of qt5-tools. Since xbps has no support for optional dependencies, I suggest splitting clang-dependant part of qt5-tools into a separate package, like qt5-tools-qdoc
If maintainers agree to this decision, I'd be happy to provide a pull-request to split qt5-tools.
```
>>> xbps-query -x musescore
qt5-plugin-sqlite>=0
libvorbis>=1.2.1rc1_1
libsndfile>=1.0.20_1
alsa-lib>=1.0.20_1
qt5>=5.6.0_1
qt5-xmlpatterns>=5.6.0_1
qt5-svg>=5.6.0_1
qt5-tools>=5.6.0_1
qt5-webengine>=5.6.0_1
zlib>=1.2.3_1
glibc>=2.28_1
portaudio>=19.20140130_1
portmidi>=217_1
libpulseaudio>=1.0_1
qt5-declarative>=5.6.0_1
libstdc++>=4.4.0_1
libgcc>=4.4.0_1
>>> xbps-query -x qt5-tools
qt5-translations>=0
desktop-file-utils>=0
hicolor-icon-theme>=0
qt5-declarative-5.11.3_3
qt5>=5.6.0_1
libstdc++>=4.4.0_1
glibc>=2.28_1
clang>=7.0.0_1
```
parent reply other threads:[~2020-09-19 23:22 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-6949@inbox.vuxu.org>]
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=20200919232254.QR2UIdZdjD26QjpihHrd2HnZewMwknsmZ1fFiMosSUI@z \
--to=pullmoll@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).