Jesse Keating wrote:
The same hyperbole can be said of any package that doesn't list a BuildRequires it needs. It will silently build and have missing functionality. Without diligent checking of the results we would miss this. Should we then just do everything installs into the buildroots so that we won't miss any functionality?
Of courses not... I think keeping a very small and condense buildroot is the right thing to do... And we should not be adding things to the buildroot to fix bugs...
No, we properly list the BuildRequires so that we have the appropriate functionality we seek. The answer is not to continue fattening the buildroots and making assumptions, the answer is to use correct packaging, correct post build QA.
Again I totally agree with you... but the question at what price? Is worth keep an buildroot the so small that it has the potential of silently creating corrupt rpms? Especially with the fix being as simple as adding two of the most common package used to do package configuration? I think the price of not added those two package much much more expensive than the disk space they will use... There is an old saying that comes to mind... penny wise and pound foolish... which I think applies here... steved. -- Fedora-maintainers mailing list Fedora-maintainers@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers -- Fedora-maintainers-readonly mailing list Fedora-maintainers-readonly@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers-readonly
