https://bugzilla.redhat.com/show_bug.cgi?id=2263790
--- Comment #25 from Petr Menšík pemensik@redhat.com --- I agree alternatives seems the correct way to choose, since those tools seems to have compatible common interface.
But because we arrive after Go project, even though it seems it is newer, I made xqp alternative name for xq tool. They are not candidates for alternatives, since they do not share common parsing options. I made yqp provided by python3-yq package and conflicting yq name provided by python3-yq-alt, which still uses alternatives. But until also golang project uses alternatives, it conflicts with yq.