https://bugzilla.redhat.com/show_bug.cgi?id=2263790
Petr Menšík pemensik@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Depends On| |2276522 Flags|needinfo?(pemensik@redhat.c | |om) |
--- Comment #17 from Petr Menšík pemensik@redhat.com --- Found out we already have xq tool in Fedora, so I cannot use xq tool name without alternatives as well. Made a post in Go based yq review [1]. In Debian they hit it too, xq-python is their name of binary. It seems at least some compability is implemented, as mentioned in [2]. So yes, alternatives might work for yq to some extent.
I have wondered where did you find nice description, which I have failed to find on upstream. It turns out your description is from concurrent yq package [3]. I do not think reusing content from different project is okay, at least without mentioning it.
I think about using just shortened binary name, yqp for python. If not used with alternatives, it would be better to type less. Anyway, turns out yq Go based command is already present in Fedora 39, not this alternative.
1. https://bugzilla.redhat.com/show_bug.cgi?id=2074467#c10 2. https://github.com/mikefarah/yq/issues/193 3. https://github.com/mikefarah/yq?tab=readme-ov-file#yq
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2276522 [Bug 2276522] Review Request: yq - Yq is a portable command-line YAML, JSON, XML, CSV, TOML and properties processor