From: hippi777 <hippi777@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Manual.md: require package names to be lowercase
Date: Fri, 16 Oct 2020 02:33:00 +0200 [thread overview]
Message-ID: <20201016003300.NhqT86y5uzooLvB6iDp4b92srkmg-uqraEKdeCgonhY@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: 1462 bytes --]
New comment by hippi777 on void-packages repository
https://github.com/void-linux/void-packages/pull/25633#issuecomment-709660487
Comment:
hi folks :)
i think it can be a strong reason to bring the package names any nearer to other distros (ok, i saw other interesting stuffs elsewhere, and i dont know enough, but it was strange when i saw the mixed case here...), and i think if this doesnt introduce any collision, then it must be doable (!=done). my 1st (naive/uneducated ?) guess would be to look up both the current name and the name with lowercase if the former cant be found, but this makes a transition period, that i dont know how long it should be...
i can understand the thinking that says if it works then it doesnt need to be fixed, but i have no idea why it was introduced on the 1st place, so, out of curiosity, why? :D
the greatest difference between all the distros out there is in their package managers and packages, bringing them any nearer to each other is a nice dream of mine, but void is the 1st distro i approached this closely, so i dunno how huge this dragon might be :D otherwise i saw the repology rules, so i have some idea :D also, a script that would install dependencies for various tasks to be done may need a nontrivial translator for package names between various distros, and while the basics will be mostly identical, i can think about nasty cases as well, so this is my other reason to vote on this change...
next prev parent reply other threads:[~2020-10-16 0:33 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 [this message]
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
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=20201016003300.NhqT86y5uzooLvB6iDp4b92srkmg-uqraEKdeCgonhY@z \
--to=hippi777@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).