FS#75195 - [go-yq] this package conflicts with commuty/yq despite being incompatible with it
Attached to Project:
Community Packages
Opened by Emanuele Torre (emanuele6) - Thursday, 30 June 2022, 08:50 GMT
Last edited by Daniel M. Capella (polyzen) - Monday, 26 September 2022, 19:23 GMT
Opened by Emanuele Torre (emanuele6) - Thursday, 30 June 2022, 08:50 GMT
Last edited by Daniel M. Capella (polyzen) - Monday, 26 September 2022, 19:23 GMT
|
Details
Description:
The versions of yq(1) provided by community/go-yq and community/yq are very different. They have different letters for command line options with similar functionality (e.g. `yq -Y' to convert JSON to YAML with `yq' and `yq -P' to do the same with go-yq) so not even such basic usage are compatible, but more importantly, community/yq is a wrapper around jq and uses jq syntax; while yq uses its own "jq like" syntax that is noticeably different. I think this package should not conflict with community/yq and should install the program it provides as go-yq. I don't think it makes much sense that, on an ArchLinux system with only packages from the official repositories, /bin/yq may be either <https://github.com/kislyuk/yq> and <https://github.com/mikefarah/yq> which are incompatible. Programs targeting ArchLinux can't reliably use /bin/yq. Packages that depend on one of these yq packages, will be incompatible with packages that depend on the other which could be avoided by naming the installed programs differently (and maybe patch programs that depend on go-yq if needed). Also, users that want play with both, have to either uninstall one, and reinstall the other (unless they also want to use them in combination), or have to install one of the two from source instead of from the official repositories. :D Cheers. ET |
This task depends upon
Closed by Daniel M. Capella (polyzen)
Monday, 26 September 2022, 19:23 GMT
Reason for closing: Won't implement
Monday, 26 September 2022, 19:23 GMT
Reason for closing: Won't implement