https://bugzilla.redhat.com/show_bug.cgi?id=979677 --- Comment #10 from Parag AN(पराग) <panemade@xxxxxxxxx> --- (In reply to Petr Šabata from comment #9) > How about the first paragraph? > > "Having proper build requirements saves the time of all developers and > testers as well as autobuild systems because they will not need to search > for missing build requirements manually. It is also a safety feature that > prevents builds with that would not otherwise fail, but would be missing > crucial features." This stands correct if mock build will fail and we add that missing BR: and build will be successful. > What if I change something in your dependency chain and your build breaks? In that case we can add manually required missing BR: > Do you prefer to wait until you get a FTBFS to listing things your package > actually uses? We can work on this when there will be FTBFS reported. > I still fail to see how this is perl specific. I will re-iterate mock is not failing so its with perl guidelines to specify that though a single dependent perl module BR: will bring perl package in buildroot, we need to write it BR: perl in spec files. > This attitude causes so much slowdown every rebuild it's ridiculous. Again, Its something that perl guidelines are missing.... -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=c6lwDSF110&a=cc_unsubscribe _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review