On Fri, Oct 07, 2011 at 11:54:19AM +0200, Johannes Meixner wrote:
And now - surprise! - surprise! - I can install the built package without an error using plain "rpm" which shows that rpm does not use the -e argument - at least not the rpm on my workstation.
I wonder why then the post build checks use the -e argument?
To catch mistakes in the scriptlets.
I would expect that the post build checks emulate what rpm does (i.e. what happens on the user's system who installs it) and not exaggerate.
No, it uses -e on purpose to force the packagers to write sane scriptlets.
From my point of view using the -e argument for the post build checks does not provide better RPM scriplets.
It only enforces packagers to add dumb "|| true" to all statements: ----------------------------------------------------------------------- %pre do_crap || true do_more_crap || true mess_up_everything || true
Your crap calls should not fail. Please fix do_crap and do_more_crap to return a correct exit code. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org