From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] python3-ansible-lint: rename to ansible-lint, update to 5.2.0.
Date: Sat, 16 Oct 2021 15:49:20 +0200 [thread overview]
Message-ID: <20211016134920.MbXQjs16ZNeAzRgq5IF9V2_s_8mg8CTFz60dNDMurQw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31998@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1336 bytes --]
New review comment by jcgruenhage on void-packages repository
https://github.com/void-linux/void-packages/pull/31998#discussion_r730266010
Comment:
> isn't really better than
I doubt most people start by searching for packages. People do `xi ${pkgname}` and if that fails, they go to the search. So I'd argue that this:
```
xi ansible-lint
Package 'ansible-lint' not found in repository pool.
```
is definitely worse that it just working.
> More, this particular proposal opens precedent to do `{python3,ruby,...}-foo` <-> `foo` rename churn, where we will have to judge if given package is library or command.
Well, sorry to say but:
- that's a bad reason IMO
- that precedent has already been set by `youtube-dl`, `xmldiff`, `subliminal`, `setconf`, `pylint`, `pex`, `httpie`, `fonttools` and `flake8`, which is just the set I've found with skimming the output of `grep -r "transitional dummy package" -C 5`, so I wouldn't be surprised if there was more.
> Existing transitional packages are either upstream renames, former functional packages that got removed (py2), or meaningful change (lua versioning).
Given the list above, this point does not hold. I'd still pledge for the rename
I can undo the rename for now to allow the updates to be merged sooner though, if we really can't agree here.
next prev parent reply other threads:[~2021-10-16 13:49 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 10:45 [PR PATCH] python3-ansible-lint: update to 5.0.12 jcgruenhage
2021-10-12 16:22 ` [PR PATCH] [Updated] " jcgruenhage
2021-10-12 17:32 ` [PR PATCH] [Updated] python3-ansible-lint: update to 5.2.0 jcgruenhage
2021-10-12 18:01 ` [PR REVIEW] " paper42
2021-10-12 18:01 ` paper42
2021-10-13 9:25 ` jcgruenhage
2021-10-13 9:29 ` jcgruenhage
2021-10-13 10:59 ` jcgruenhage
2021-10-13 11:41 ` jcgruenhage
2021-10-13 12:59 ` [PR PATCH] [Updated] " jcgruenhage
2021-10-13 15:03 ` [PR PATCH] [Updated] python3-ansible-lint: rename to ansible-lint, " jcgruenhage
2021-10-13 15:09 ` jcgruenhage
2021-10-13 16:45 ` [PR REVIEW] " Chocimier
2021-10-13 16:48 ` Chocimier
2021-10-13 16:48 ` Chocimier
2021-10-13 16:48 ` Chocimier
2021-10-13 17:30 ` jcgruenhage
2021-10-13 17:35 ` jcgruenhage
2021-10-13 18:10 ` jcgruenhage
2021-10-13 18:10 ` [PR PATCH] [Updated] " jcgruenhage
2021-10-14 16:29 ` [PR REVIEW] " Chocimier
2021-10-14 16:29 ` Chocimier
2021-10-14 16:29 ` Chocimier
2021-10-14 16:30 ` Chocimier
2021-10-14 17:12 ` jcgruenhage
2021-10-14 20:02 ` [PR PATCH] [Updated] " jcgruenhage
2021-10-14 20:04 ` jcgruenhage
2021-10-14 20:12 ` jcgruenhage
2021-10-14 20:12 ` [PR REVIEW] " jcgruenhage
2021-10-14 20:13 ` jcgruenhage
2021-10-14 20:22 ` [PR PATCH] [Updated] " jcgruenhage
2021-10-14 21:26 ` [PR REVIEW] " jcgruenhage
2021-10-15 16:22 ` Chocimier
2021-10-15 16:23 ` Chocimier
2021-10-15 19:56 ` [PR REVIEW] " paper42
2021-10-16 13:49 ` jcgruenhage [this message]
2021-10-16 14:06 ` [PR PATCH] [Updated] " jcgruenhage
2021-10-19 14:37 ` jcgruenhage
2021-10-19 15:11 ` jcgruenhage
2021-10-19 19:22 ` jcgruenhage
2021-10-19 19:29 ` [PR REVIEW] " jcgruenhage
2021-10-22 20:14 ` [PR REVIEW] python3-ansible-lint: update to 5.2.1 Chocimier
2021-10-23 10:51 ` [PR PATCH] [Updated] " jcgruenhage
2021-10-23 10:51 ` [PR REVIEW] " jcgruenhage
2021-10-23 20:37 ` [PR PATCH] [Merged]: " Chocimier
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=20211016134920.MbXQjs16ZNeAzRgq5IF9V2_s_8mg8CTFz60dNDMurQw@z \
--to=jcgruenhage@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).