From: st3r4g <st3r4g@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: mesa: remove dummy transitional packages
Date: Sat, 11 Apr 2020 22:18:05 +0200 [thread overview]
Message-ID: <20200411201805.UhH7h4La0Asbys7XkWqgNpzJIsFNMK9SSDNtfxn3Jzo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20889@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 775 bytes --]
New comment by st3r4g on void-packages repository
https://github.com/void-linux/void-packages/pull/20889#issuecomment-612504870
Comment:
Well this is not what I meant in #20861. I suggested to purge the obsolete `mesa-*-dri-dbg` binary packages (only repoadmins can do this), not the dummy templates, that are still required for people who have not updated yet their system after the reorganization. It's been only ~5 months, maybe it's better to wait a bit more.
> Perhaps the only packages that could be advantageous to keep would be those that have dependencies beyond mesa-dri. Like the Intel, Nouveau and ATI ones.
I made them like that because e.g. `mesa-intel-dri` had vulkan inside, so that users would get the equivalent new packages after the reorganization.
next prev parent reply other threads:[~2020-04-11 20:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-11 19:57 [PR PATCH] " ericonr
2020-04-11 20:13 ` [PR PATCH] [Updated] " ericonr
2020-04-11 20:14 ` st3r4g
2020-04-11 20:15 ` st3r4g
2020-04-11 20:15 ` st3r4g
2020-04-11 20:17 ` st3r4g
2020-04-11 20:17 ` st3r4g
2020-04-11 20:18 ` st3r4g [this message]
2020-04-11 20:18 ` st3r4g
2020-04-11 20:20 ` ericonr
2020-04-11 20:21 ` st3r4g
2020-04-11 20:22 ` st3r4g
2020-04-11 20:26 ` [PR PATCH] [Closed]: " ericonr
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=20200411201805.UhH7h4La0Asbys7XkWqgNpzJIsFNMK9SSDNtfxn3Jzo@z \
--to=st3r4g@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).