[Rpm-ecosystem] Trying to understand %buildsubdir and debuginfo generation

[Jeff Johnson]

On Apr 26, 2018, at 11:47 PM, Jason L Tibbitts III <tibbs at math.uh.edu> wrote:

>>>>>> "JJ" == Jeff Johnson <n3npq at me.com> writes:
> 
> JJ> Note that the macro definitions you are trying to understand are not
> JJ> from rpm itself (so you perhaps should be consulting with other
> JJ> SME's than me).
> 
> Well, I was consulting a mailing list.
> 
> Here's a paste from the macros.debug file in the rpm 4.14.1 source:
> 
> %install %{?_enable_debug_packages:%{?buildsubdir:%{debug_package}}}\
> %%install\
> %{nil}
> 
> Here's a paste from the macros that Fedora uses
> (/usr/lib/rpm/redhat/macros):
> 
> %install %{?_enable_debug_packages:%{?buildsubdir:%{debug_package}}}\
> %%install\
> %{nil}
> 
> Seems... similar.
> 
> JJ> Talk to whomever decided that there was a need to overload %install
> JJ> with a test on %buildsubdir.
> 
> OK, so, again, I'm trying to talk to this mailing list, which I thought
> provided the best chance to reach the people who know.
> 

I recuse myself, largely because the current implementation of -debuginfo has convolved the (known!) flaws of the rpm spec file parser with automagic -debuginfo generation (splitting sources into multiple packages forces handling of painful *.spec constructs like %exclude within the side effect driven spec file parser and worse).

Good luck!

73 de Jeff
> - J<
> _______________________________________________
> Rpm-ecosystem mailing list
> Rpm-ecosystem at lists.rpm.org
> http://lists.rpm.org/mailman/listinfo/rpm-ecosystem