[Rpm-maint] [rpm-software-management/rpm] RFE: BuildRequires generator (#104)

[nim-nim]

> I'm not sure calculating "fixed point" for build requires dependency graph is required in the first place. Having BuildRequires and then single-step dynamic build requires would be powerful enough I think, and easier to implement from buildsystem pov.

To be honest, I don't think I need looping for Go, but I'm not sure I won't need it either (the Go dep situation is evolving fast those days as things have reached a "can't continue like before" point).

The "correct" future-proof way to do it is looping (for IT definitions of future-proof, that is)

> Slight benefit would be that packagers would be much less motivated to do **very complicated magic** in build-depsolving.

I'm not fearing packagers as much as upstream language ecosystems. Sure, some packagers will write their own custom BR logic but most major languages will just call upstream language tools in  %buildrequires (without _ please, so it's consistent with %buildroot and other historical rpm bits)

With git clone so easy nowadays I'm pretty sure some of them will bake multi-phase dep resolving in their languages sooner or later (if not already done). I'd rather not have a brand-new dynamic BR that lasts a month before they obsolete it.

-- 
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/issues/104#issuecomment-366430457
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20180217/48dfcf45/attachment-0001.html>