From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Many templates unnecessarily makedepend on MesaLib-devel
Date: Sun, 01 May 2022 04:13:48 +0200 [thread overview]
Message-ID: <20220501021348.Qy6rgSxRS_mtTqWcFJ_6AlgGuQmbSYlO8oQxHsri6jg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23243@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 676 bytes --]
Closed issue by st3r4g on void-packages repository
https://github.com/void-linux/void-packages/issues/23243
Description:
The switch to glvnd has moved the GL headers from `MesaLib-devel` to `libglvnd-devel`. Most applications don't need all the mesa-specific stuff provided by `MesaLib-devel`, so their `makedepends` could be optimized.
- Applications rendering with GL generally only require `libglvnd-devel`.
Example: `cairo`
- Applications with special requirements on the buffers they allocate (e.g. Wayland compositors) use also `gbm`, a tiny library currently part of `MesaLib-devel`, that would be better split into its own `libgbm-devel`.
Example: `wlroots`
parent reply other threads:[~2022-05-01 2:13 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23243@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=20220501021348.Qy6rgSxRS_mtTqWcFJ_6AlgGuQmbSYlO8oQxHsri6jg@z \
--to=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).