Description of problem:

as per documentation:
http://dnf-plugins-core.readthedocs.org/en/latest/builddep.html

  Build dependencies in a package (i.e. src.rpm) might be different than 
  you would expect because they were evaluated according macros set on 
  the package build host.

Steps to Reproduce:

On an x86_64 hardware and distro:

  dnf download systemd --source
  dnf builddep systemd
  ...
  rpmbuild -ba systemd.spec


Actual results:

gnu-efi gnu-efi-devel build dependencies are missing

Expected results:

all the build dependencies are installed.


Additional info:

systemd.spec contains

%ifarch %{ix86} x86_64
BuildRequires:  gnu-efi gnu-efi-devel
%endif

I am aware of the documentation which states that

> Build dependencies in a package (i.e. src.rpm) might be different than you would expect because they were evaluated according macros set on the package build host. (lame excuse ;)

However this is not completely satisfactory. If we want to automatize the packaging of our rpms, this will mean additional configuration to get a per-package list of additional dependencies. Additionally, I don't think we should expect everyone to go read the documentation for a tool as straightforward as "builddep" that just works most of the times. It makes the tool feel unreliable and degrades the user experience.

If this is a WONTFIX, could we please update the documentation to say so, or maybe point to another bugzilla record?