[Rpm-maint] [rpm-software-management/rpm] debuginfo generation does not work with --build-in-place (Issue #3042)

[Zbigniew Jędrzejewski-Szmek]

> Only with --short-circuit we "poison" the produced packages to prevent people from distributing them (accidentally or otherwise).

It is a misfeature. It means that the produced packages cannot be compared and tested properly. In particular, `--short-circuit` is very often used to test details of `Obsoletes` and `Requires` and such. Not being able to produce the package that looks *exactly* like the normal output makes the build not useful.

The whole idea of "prevent people from distributing them" doesn't make much sense. You cannot build a package with `--short-circuit` "accidentally". It's a very long option that you need to insert in the right place. And I guess "otherwise" means "maliciously" here, and that's even less useful, because the person doing the build has full control over what is built, so they don't need to use `--short-circuit` to achieve malicious goals.

Instead of using `--short-circuit`, people are forced to either wait for full package builds (which can be hours), or do dirty tricks like comment out part of the spec file. Those solutions are much worse (and much more likely to go wrong), than the problem being solved, i.e. people forgetting that they used `--short-circuit` and distributing those packages.

Please drop this whole protection and let people use `--short-circuit` without any limitations.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/3042#issuecomment-2074531384
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/issues/3042/2074531384 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20240424/6d93e8d6/attachment-0001.html>