Because in %post $RPM_BUILD_ROOT turns out to be "/", so in this spec,I used directly %{_tmppath}/%{name}-%{version}-%{release}-root instead of $RPM_BUILD_ROOT
rpm -Uvh %{_tmppath}/%{name}-%{version}-%{release}-root%{bundledir}/log4c-1.2.1-1.i386.rpm
rpm -Uvh %{_tmppath}/%{name}-%{version}-%{release}-root%{bundledir}/abc-1.0-1.i386.rpm
I checked the existence of log4c-1.2.1-1.i386.rpm and abc-1.0-1.i386.rpm in %{_tmppath}/%{name}-%{version}-%{release}-root%{bundledir} and they are there.
I need an all-in-one installer , not 2 single installer. Thank Nigel for your reply.
-----Original Message-----
From: rpm-list-bounces@xxxxxxxxxxxxx [mailto:rpm-list-bounces@xxxxxxxxxxxxx] On Behalf Of Nigel Metheringham
Sent: Thursday, July 23, 2009 5:09 PM
To: General discussion about the RPM package manager
Subject: Re: RPM package bundle problem.
At the point when you run the %post the files are *not* in
$RPM_BUILD_ROOT but instead under root (/).
Plus you should not be running another rpm transaction within an rpm
transaction - it might work (depending on the version of rpm), or it
might fail with locking issues, or it might completely corrupt your
rpm database.
You should do this with dependancies and a proper package management
tool (ie yum etc) rather than abusing raw rpm.
Nigel.
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxxxxx
http://lists.rpm.org/mailman/listinfo/rpm-list
