| Summary: | Consider letting "dnf some.spec" default to "dnf builddep some.spec" | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Marja Van Waes <marja11> |
| Component: | RPM Packages | Assignee: | Neal Gompa <ngompa13> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Normal | Keywords: | UPSTREAM |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | dnf-1.1.8-2.mga6 | CVE: | |
| Status comment: | |||
This is not really possible, as the DNF CLI is implemented as a series of subcommand files that control various actions. On top of it, the "builddep" functionality isn't actually in the DNF core, but in the core plugins. An equivalent would be that "dnf install /path/to/some.spec" would trigger builddep functionality (as urpmi expands to User RPM Installer), but unless the decision is made to move builddep functionality into the DNF core, I don't see this happening. As DNF 2.0 discussions are happening now, we'll see how that shakes out, but for now, this is not likely to happen. Status:
NEW =>
RESOLVED
Rémi Verschelde
2016-05-10 10:02:14 CEST
Keywords:
(none) =>
UPSTREAM |
"urpmi /path/to/some.spec" defaults to "urpmi --buildrequires /path/to/some.spec" If one day you're bored, and there is really nothing more important to do, then please consider letting "dnf /path/to/some.spec" default to "dnf builddep /path/to/some.spec"