On Tue, 11 Oct 2022 at 07:54, Panu Matilainen <[email protected]> wrote:
> On 10/10/22 10:15, Jaroslav Mracek wrote: > > Please can you be more specific which kind of functionality is required > for particular command? Why is it important to know what user case you want > to resolve it? Commands has multiple options and some of them could be > unused. Specially repoquery has tons of options. Knowing critical usercase > will help us a lot to not only provide the same option but to improve DNF5 > behavior in comparison to DNF4. > > > > I recommend to create for each user case or command an issue - > https://github.com/rpm-software-management/dnf5/issues. Please provide as > much as possible information to understand the user case to be able to set > a proper priority. > > The mission of repoquery is basically to provide scriptable access to > all available repository metadata. That necessarily involves helluva > many switches, added over time to address all manner of use-cases. Don't > assume anything is there just for giggles. > Maybe it makes sense to put it just as a dedicated command like I thought it was until 'recently (*cough* sorry N years ago *cough*)'. -- Stephen Smoogen, Red Hat Automotive Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren
_______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
