De: "nicolas mailhot" À: "Jan Chaloupka" >> I mentioned a list of things that you did not answer fully. Most important to me: >> - your macros do not generate build-time dependencies, which I see as >> one of the drawbacks. > Generating BuildRequires dynamically needs changes in rpm tooling (mostly mock, I think). So it can not be done today if I'm not wrong. If you have a tool that outputs BuildRequires outside rpm, you can still use it. That's not an > absolute showstopper as the go compiler is pretty explicit on what's missing, so BuildRequires are easily added during the first %build or %check run (though that's tedious and annoying). >> Do you plan to ignore them? >Generating BuildRequires would be quite easy if rpm tooling provided an entry point at the end of %prep. So, that's a mid-term objective and requires sending an RFE mock-side first. And that part is done: https://github.com/rpm-software-management/mock/issues/160 Feel free to complete/correct/support the request so it has a change to be taken into account and we can start working on integrated Go BuildRequires Regards -- Nicolas Mailhot _______________________________________________ packaging mailing list -- packaging@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to packaging-leave@xxxxxxxxxxxxxxxxxxxxxxx
