On Tue, 30 Apr 2019 at 21:04, Neal Gompa <ngompa13@gmail.com> wrote:
> And what is wrong with just "BuildRequires: pkgconfig"?

That is no guarantee that '/usr/bin/pkg-config' will be provided,
which is required by the dep generator and various tools.

You just put in my hand +1 to not use paths in BuildRequires.
+1 for me. Thx.
If you will look across /usr/lib/macros and files in /usr/lib/rpm/macros.d you will find hundreds of other commands used with full path and only occasionally some of them are used in BRs in form "BuildRequires: /some/path/command".
Are going to request/propose to change whole distribution pattern of BRs? Really?
FYI: We call that thing which you are refusing to use .. abstraction.
> Don't you see that this forces dependencies resolution to use packages files list?

This is free already, as that data is always part of the solver cache.

Besides, there is no ban on paths that are provided by primary.xml
(*/bin, */sbin, */lib(64|exec), /etc). The ban is basically pointless,
but that's what it is.

<counerargument=WRONG>
rpmbuild is not using dnf xml files :-/
</counerargument>

> IIRC Fedora already had policy to not use paths in BRs.

Outside of paths already provided in primary.xml, packagers SHOULD NOT, yes.

You are again talking about install package time dependencies resolution.
Command rpmbuild which is processing spec files is using rpm database.
We are talking about packages build time dependencies resolution.
Please do me a favourite and execute on your system from root "rpm --rebuilddb; ls -l /var/lib/rpm/{Basenames,Providename}" and answer on the question: query to which one rpm table has chance to be shorter?

kloczek
-
Tomasz Kłoczko | LinkedIn: http://lnkd.in/FXPWxH