[Rpm-maint] [rpm-software-management/rpm] Add support for special system-level %include path (#685)

[Panu Matilainen]

> I wish `%_rpmincludedir` was externaly configurable somehow, e.g. by env variable or cmd line option. Otherwise it will make life harder to SCLs, where everything should go into /opt.

It's a macro. You can --define it to whatever you like.

> What is the use case anyway? I can imagine using this for including pre-generated changelogs, but again, it would need to be configurable ...

Sorry, I assumed it was kinda obvious: to share whatever common pieces between packages in an ecosystem, to put it broadly. An ecosystem could be a programming language, or extension to a specific program/library, etc. Currently such things are stuffed into macro files in /usr/lib/rpm/macros.d/ but there are various problems with this:
- there's no build-require trace of where those macros come from
- macro files have limitations that spec includes don't (eg conditionals)
- those macros are loaded on every single rpm invocation for no good reason

So the idea is that, say, Python 3 package on a distro would do something like
```%include <python3.inc>```
...which will automatically create a build-dependency on the path where that file comes from - presumably python3-devel. And even if we skipped the automatic dependency, it creates a strong trace as to what macros this package needs. Much more so than the current automatically loaded stuff does.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/685#issuecomment-487487496
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20190429/e91196f6/attachment.html>