On Wed, 30 Mar 2005 14:54:09 -0500, caffeine1@xxxxxxxxx
<caffeine1@xxxxxxxxx> wrote:
> Well, I just found the answer on my own to my original question:
>
> 1. gzip the files to be protected during the %install phase
> 2. gunzip them during the %post phase (and be sure to --force it)
>
Danger Will Robinson, Danger!
If you do that then expect "rpm -V borked.rpm" will never have a
chance of being clean. The checksums on these files would have been
made against the gzipped files, not the once you unzip later at, gulp,
install time.
The right thing to do is in your spec fil or (/etc/rpm/macros or
~/.rpmmacros) is to do:
%define %__spec_install_post %{nil}
Or redefine it to your liking it. If you run:
rpm --eval '%{__spec_install_post}'
You can see what it is defined as on your build system. This text is
tacked onto the end of your %install scriptlet.
Now I do something sneaker than this, though, which I discovered by accident.
At the end of my %install I do:
exit 0
Which becomes:
exit 0
%{__spec_install_post}
which effectively short circuits it...but don't follow my hackish examples (-;
Cheers...james
> I know, I know: "Well, duh." Very simple fix.
>
> _______________________________________________
> Rpm-list mailing list
> Rpm-list@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/rpm-list
>
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list
