How to enable and disable debug packages?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Like I said earlier, I'm now looking into the "debuginfo" package mechanism of rpm/redhat-rpm-config. I think I'll have to ask an old question again in this context, i.e.:

How do you enable and disable debug package build?

I found a way of disabling them a long time ago, of course, which was just to insert

%define debug_package %{nil}

in the rpm spec or

%debug_package %{nil}

in /etc/rpm/macros.

Now that I'm actually trying to build debuginfo packages, I'm no longer happy with that solution, however. Neither do I want to globally enable debuginfo, I think, as it just gets in the way for general rebuilds of freeware src.rpms etc, and also fails for far too many packages. What I'd really like, is to keep the mechanism off by default, but allow it to be re-enabled for on a package-by-package basis by including a %define in the .spec file, or a --define on the command line. The problem is, debug_package is not very easy to use that way, as it has very complex body including the full definition of the package. Also, after reading the Red Hat macro setup, I thought that %_enable_debug_packages might be used as a simple flag, but unsetting it appears to have no effect (i.e. debuginfo is still built, provided that %debug_package is set.)

So is there a predefined way to enable/disable debuginfo build as mentioned above? Or do I have to introduce some additional macro logic of my own to be able to do this?

- T

_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list

[Index of Archives]     [RPM Ecosystem]     [Linux Kernel]     [Red Hat Install]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Red Hat]     [Gimp]     [Yosemite News]     [IETF Discussion]

  Powered by Linux