[Rpm-maint] [rpm-software-management/rpm] Dynamic Build Dependencies (#593)

[nim-nim]

> Mock will have to parse output of rpmbuild - in case the rpmbuild fails due ` %generate_buildrequires`. Parsing the output for `_("Failed build dependencies:\n")` is suboptimal. Especially because of `_()` and because `rpmpsPrint()` use `fprintf(f, "\t%s\n", msg);`. Can I have something machine friendly? Either:
> 
>     * `--parse` - Optimize the command output for easy parsing. Where the packages are on one line, comma separated. And the line is not localized.
> 
>     * `--generate_buildrequires-to-file` `FILE` which will put the needed build requires to separated file. (This needs to be documented how to interpret `--root` option)
> 
>     * or something else

I’m not sure the comma separated line is a good idea, sooner of later someone will need to generate build dependencies  with complex constrains (at least version constrains, maybe even rpm rich deps). One failing construct per line is always going to be simpler to understand.

And the file option is probably going to be a bit too restrictive for some use cases.

How about just prefixing each missing build dependency line with a prefix you can lock on? Just

```
Failed build dependencies:(localised)
BuildDep: <some rpm dep construct>
BuildDep: <some rpm dep construct>
```
As long as rpmbuild never outputs a line starting with `BuildDep:` for any other reason, that should be easy for you to lock on. And still human-friendly.

-- 
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/593#issuecomment-443788074
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20181203/2977945e/attachment-0001.html>