[Rpm-maint] [rpm-software-management/rpm] Dynamic Build Dependencies (#593)
nim-nim
notifications at github.com
Fri Nov 30 14:09:10 UTC 2018
> I am not at all against having scripts for normal dependency generation. But their are a few important differences to the BuildRequires:
>
> * They have to be attached to a sub package and cannot be global
>
> * We may want to (be able to) associate the script to files - so we need a way of passing the fileattr macros (path, flags, magic).
>
> * They don't need the funky stop build, install new deps and restart build cycle
> So they need to be done a different way as the %generate_buildrequires script anyway. So while I agree we should add those it is probably best to concentrate on the topic at hand first.
>
>
> Also not sure if %generate_buildrequires vs %generate buildrequires really makes a lot of difference.
>From a human interface POW both are awful
I can name the macro designed to be executed in prep `%goprep`, the one designed to be executed in build `%gobuild` and so on, but
`%go_generate_buildrequires` ? A third of the line is gone without even injecting a single argument
And go is lucky, it only needs two-letters for prefixing, other languages/ecosystems eat more letters.
--
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-443214064
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20181130/0d022de3/attachment.html>
More information about the Rpm-maint
mailing list