-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement provides command #147
Comments
dnf commands provides/whatprovides together with options --provides/--whatprovides are pretty confusing. It'd be nice to reduce this confusion in dnf5. How about marking "provides" command as obsoleted (without any aliases) and suggest to use the options instead? |
I understand what you mean. But I'm in favor of keeping at least the "provides" subcommand. I don't use "whatprovides" or any of the flags. I think there are already to many flags and using a subcommand is much easier to learn as I know some that use "provide" as well. It's also nice for tab completion. |
@glum23
|
The command is implemented. No alias were implemented. I would like to
|
With DNF4 it works:
|
something must be wrong on my side then |
Doesn't your laptop use a different architecture? |
it does, I tried it on aarch too |
|
works. I am confused now. why do I have to use for example, this would work
but not this
|
I am closing this as all |
Command:
provides
Aliases:
prov
,whatprovides
,wp
whatprovides
or no aliases at alldnf [options] provides <provide-spec>
Finds the packages providing the given
<provide-spec>
. This is useful when one knows a filename and wants to find what package (installed or not) provides this file. The<provide-spec>
is gradually looked for at following locations:<provide-spec>
is matched with all file provides of any available package:<provide-spec>
is a system command, prepends it with/usr/bin/
,/usr/sbin/
prefixes (one at a time) and does the file provides search again. For legacy reasons (packages that didn’t do UsrMove) also /bin and /sbin prefixes are being searched:This command by default does not force a sync of expired metadata. See also Metadata Synchronization.
The text was updated successfully, but these errors were encountered: