Mailinglist Archive: opensuse-packaging (183 mails)

< Previous Next >
Re: [opensuse-packaging] spec_install_post
  • From: Ruediger Oertel <ro@xxxxxxx>
  • Date: Wed, 3 Jun 2009 02:04:06 +0200
  • Message-id: <200906030204.07377.ro@xxxxxxx>
On Tuesday 02 June 2009 10:41:37 Wolfgang Rosenauer wrote:
Hi,

I'm wondering what the following does and if it works in openSUSE (and
in which version if so): (seen in a Fedora spec file)

%define __spec_install_post \
%{?__debug_package:%{__debug_install_post}} \
%{__arch_install_post} \
%{__os_install_post} \
some \
commands \
%{nil}

__spec_install_post is what rpm expands at the end of the install section of a
specfile.
The generic definition of this one is (from /usr/lib/rpm/macros):
%__spec_install_post\
%{?__debug_package:%{__debug_install_post}}\
%{__arch_install_post}\
%{__os_install_post}\
%{nil}

so what the above does is that it inserts a few commands at the very end
of the install section, after for example all the brp-scripts have run, which
are usually part of one of the referenced macros above (__os_install_post)

It's apparently supposed to fix an issue I have currently solved by
using fragile %post install scriptlets.
I have binary files in the package for which I need something like
checksums calculated and saved in another files. I couldn't create them
in the build or install steps because they get changed when debuginfo is
extracted.

no guarantees, but it should work for exactly that purpose: to get after the
debuginfo/strip sequence.


--
with kind regards (mit freundlichem Grinsen),
Ruediger Oertel (ro@xxxxxxxxxx,ro@xxxxxxx,bugfinder@xxxxxxxxxxx)
----------------------------------------------------------------------
Linux MacBookRudi 2.6.30-rc6-git3-4-default #1 SMP 2009-05-25 14:11:59 +0200
x86_64
Key fingerprint = 17DC 6553 86A7 384B 53C5 CA5C 3CE4 F2E7 23F2 B417
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG N├╝rnberg)
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging+help@xxxxxxxxxxxx

< Previous Next >
References