I think I figured this out. When the source is already present in the build directory, a fairly generic spec file is generated by ltib for creating the rpm. If it gets built from clean sources, the package spec file is used. This would help to distinguish between a "dev build" and a regular clean build when you do an rpm query on the target system.
Thanks, Bruce
On Thu, Mar 3, 2011 at 12:12 PM, Stuart Hughes <address@hidden> wrote:
Hi Bruce,
I don't understand. What are you seeing that you don't want to see?
BTW: don't use -f it's only needed under exceptional circumstances
(e.g. full-rebuild by an auto builder).
Regards, Stuart
On 01/03/11 21:09, Bruce wrote:
Hi again,
I have been leveraging ltib to generate rpm's for our
software by simply using "./ltib -p name -f".
We use rpm on the target board to install it. After the
install, I do "rpm -qi name" and it prints out information not
in my spec file. Ltib generates a spec file. How can I just get
my package to build stand-alone and have the correct information
after install?