On Tue, Jun 4, 2024 at 4:24 AM Sandro Mani <manisan...@gmail.com> wrote:
>
>
> On 04.06.24 10:12, Daniel P. Berrangé wrote:
> > On Tue, Jun 04, 2024 at 08:40:15AM +0200, Sandro Mani wrote:
> >> Hi
> >>
> >> In rpm 4.20 as currently available in rawhide, defining 
> >> __debug_install_post
> >> seems to have no effect. The %mingw_package_header sets 
> >> __debug_install_post
> >> as follows
> >>
> >> %mingw_package_header                                         \
> >> %global __strip %{mingw_strip}                                \
> >> %global __objdump %{mingw_objdump}                            \
> > FWIW, I don't think these two overrides should be required
> > anymore. The standard strip/objdump commands in /usr/bin
> > work with PE files these days, and for the pacakges where
> > we have merged mingw+native specs these overrides aren't
> > used.
> >
> > Given that, I'd question whether %mingw_package_header needs
> > to continue to exist either ? it is no harder / great lines
> > of code to simply call %mingw_debug_install_post in %install,
> > thus avoiding the rpm 4.20 compat issue.
>
> We could indeed to that, as we already require for unified native/mingw
> specs. Perhaps there also exists a way to trigger this automatically
> with a mechanism similar to the %{_rpmconfigdir}/fileattrs/*.attr?
>

I don't know about that, we don't yet have subpackage generators. But
we *do* have the ability to run scripts to make spec snippets that
rpmbuild picks up for dynamic packaging.




--
真実はいつも一つ!/ Always, there's only one truth!
--
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to