On Sun Feb 12, 2023 at 13:40 +0000, Maxwell G via devel wrote: > > Though, it would be nice to have an easier subcommand or option just for > > that, as it will be, I think, the most required use case. Maybe a 'fedrq > > whatrequires --soname-bump SRCNAME'? > > Thanks for trying it out and for the feedback! I don't want to tack this > on to `whatrequires`, but a separate subcommand might be warranted. Name > suggestions are welcome. subpkgs-whatrequires is accurate but way too > long :). I created an issue for this in fedrq's issue tracker [1]. > > > [1] https://todo.sr.ht/~gotmax23/fedrq/13 > This is now available on the main branch. $ fedrq whatrequires -F source $(fedrq subpkgs SRCNAME) can be replaced with $ fedrq whatrequires-src -F source SRCNAME or $ fedrq wrsrc -F source SRCNAME wrsrc is an alias for whatrequires-src. If you want, you can install https://copr.fedorainfracloud.org/coprs/gotmax23/fedrq-dev/build/5519594/ or $ pip install 'git+https://git.sr.ht/~gotmax23/fedrq#main' to try it out. I'll cut a release later this week. -- Maxwell G (@gotmax23) Pronouns: He/They _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
