From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: rename `gpgmeqt` -> qgpgme-qt5
Date: Thu, 21 Mar 2024 11:47:52 +0100 [thread overview]
Message-ID: <20240321104752.42D5D21499@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49293@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/49293#issuecomment-2011911693
Comment:
I didn't realize that the Qt5 package was nothing more than a library. We have a [naming convention](https://github.com/void-linux/void-packages/blob/master/Manual.md#libraries) that should be applied to any new subpackage here. The new addition ought to be called `libqgpgmeqt6{,-devel}` or, because that's an illegible jumble of Q, P and G, maybe `libqgpgme-qt6{,-devel}`.
Still, changing the name of the existing subpackage is a bad experience, because
1. We'll still have to carry the current name anyway, as a transitional dummy;
2. Presumably the Qt5 package should just be phased out at some point; and
3. Package renames should really only be considered when the upstream project actually changes its name, not to correct our own (longstanding) violations of convention.
prev parent reply other threads:[~2024-03-21 10:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 17:21 [ISSUE] " Luciogi
2024-03-20 18:02 ` [ISSUE] [CLOSED] " ahesford
2024-03-20 18:02 ` ahesford
2024-03-21 6:33 ` Luciogi
2024-03-21 6:48 ` classabbyamp
2024-03-21 7:01 ` Luciogi
2024-03-21 10:47 ` ahesford
2024-03-21 10:47 ` ahesford [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=20240321104752.42D5D21499@inbox.vuxu.org \
--to=ahesford@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).