Bug 18344 - Consider letting "dnf some.spec" default to "dnf builddep some.spec"
Summary: Consider letting "dnf some.spec" default to "dnf builddep some.spec"
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Neal Gompa
QA Contact:
URL:
Whiteboard:
Keywords: UPSTREAM
Depends on:
Blocks:
 
Reported: 2016-05-03 19:54 CEST by Marja Van Waes
Modified: 2016-05-10 10:02 CEST (History)
0 users

See Also:
Source RPM: dnf-1.1.8-2.mga6
CVE:
Status comment:


Attachments

Description Marja Van Waes 2016-05-03 19:54:40 CEST
"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"
Comment 1 Neal Gompa 2016-05-04 16:10:57 CEST
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
Resolution: (none) => WONTFIX

Rémi Verschelde 2016-05-10 10:02:14 CEST

Keywords: (none) => UPSTREAM


Note You need to log in before you can comment on or make changes to this bug.