From: the-eater <the-eater@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Manual.md: require package names to be lowercase
Date: Thu, 17 Jun 2021 13:55:46 +0200 [thread overview]
Message-ID: <20210617115546.Ew6YxTp1beYX-uleF3nBmHZ4hgpbwimgIJOvXJKt3m4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25633@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 905 bytes --]
New comment by the-eater on void-packages repository
https://github.com/void-linux/void-packages/pull/25633#issuecomment-863176040
Comment:
I personally don't really care how the packages are stored repo side,
I do however get very annoyed by trying to install a package, xbps telling me it doesn't exist and then searching it only to find out it uses random capitals, it's inconsistent and annoying.
I have proposed this in IRC and I think it would align with @Gottox wishes partly as well. (since it would mean overhauling strings a bit)
I would rather have the package matching to be case-insensitive, I assume there's at least consensus that we shouldn't have e.g. `MyPackage` and `mypackage` at the same time.
allowing package matching to be case-insensitive allows usage pattern to be the same as if all was lowercase, and might ease migration if we plan to go full lowercase anyhow
next prev parent reply other threads:[~2021-06-17 11:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 10:27 [PR PATCH] " Piraty
2020-10-15 17:15 ` the-maldridge
2020-10-15 17:50 ` q66
2020-10-15 17:56 ` Chocimier
2020-10-15 18:03 ` q66
2020-10-15 18:03 ` the-maldridge
2020-10-15 18:05 ` Duncaen
2020-10-15 18:05 ` q66
2020-10-15 18:06 ` Chocimier
2020-10-15 18:07 ` q66
2020-10-15 18:25 ` leahneukirchen
2020-10-15 18:36 ` Chocimier
2020-10-15 18:36 ` Chocimier
2020-10-15 18:38 ` Duncaen
2020-10-15 18:50 ` Chocimier
2020-10-15 19:03 ` Duncaen
2020-10-16 0:33 ` hippi777
2020-10-16 4:28 ` CameronNemo
2020-10-16 4:28 ` CameronNemo
2020-10-16 4:30 ` CameronNemo
2020-10-16 4:30 ` CameronNemo
2020-10-16 4:31 ` CameronNemo
2020-10-16 4:31 ` CameronNemo
2020-10-16 9:50 ` Gottox
2020-10-22 14:52 ` Piraty
2020-10-22 14:52 ` [PR PATCH] [Closed]: " Piraty
2020-10-22 15:22 ` q66
2020-10-22 15:39 ` q66
2020-10-22 17:52 ` Chocimier
2020-12-14 18:29 ` ericonr
2021-06-17 11:55 ` the-eater [this message]
2021-06-17 12:16 ` the-eater
2022-04-21 2:12 ` github-actions
2022-05-06 2:08 ` [PR PATCH] [Closed]: " github-actions
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=20210617115546.Ew6YxTp1beYX-uleF3nBmHZ4hgpbwimgIJOvXJKt3m4@z \
--to=the-eater@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).