From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: graphviz: separate x11 binaries and gtk plugin to reduce deps
Date: Mon, 20 Sep 2021 19:52:34 +0200 [thread overview]
Message-ID: <20210920175234.hWQz5lO0UP6uLIsfMhSbmeo4AFP9_pEA3dZO88fo_kw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32939@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 810 bytes --]
There's a merged pull request on the void-packages repository
graphviz: separate x11 binaries and gtk plugin to reduce deps
https://github.com/void-linux/void-packages/pull/32939
Description:
See #32826.
Arguably, the split of x11 is less important. It saves from `libXaw`, `libXmu` and `libXt`, but `libX11` and `libXrender` are deps via `cairo` anyway.
The split of `gtk` saves a lot of deps which are not usually installed on a server or chroot.
It is possible to make a smaller pkg without `gd`, `rsvg` and `webp` which seems good enough (renders svg and ps via core plugin, images and pdf via cairo), but probably not worth it.
Can't remove `pango` without disabling `cairo` as well; in this case one would want to keep `gd` for images. I wouldn't do this since the gd plugin is deprecated.
prev parent reply other threads:[~2021-09-20 17:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-11 23:59 [PR PATCH] " tornaria
2021-09-12 13:39 ` [PR PATCH] [Updated] " tornaria
2021-09-12 13:42 ` tornaria
2021-09-12 13:43 ` tornaria
2021-09-20 16:37 ` [PR PATCH] [Updated] " tornaria
2021-09-20 16:49 ` tornaria
2021-09-20 17:52 ` leahneukirchen [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=20210920175234.hWQz5lO0UP6uLIsfMhSbmeo4AFP9_pEA3dZO88fo_kw@z \
--to=leahneukirchen@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).