I am using/testing RPM 4.0.3 to build packages as root and have found some weird inconsistencies. Or perhaps it's my naivety to the tool.
1) When I direct RPM to build the package in a different build area other than /usr/src/redhat/.. it will only use the different BuildRoot directive if I have a .rpmmacros file in my ~ dir (/root). Why won't a .rpmrc file or a rpm bb --buildroot options work for me? 2) The ....--buildroot option will not be recognized with the # rpm command but will be with a # rpmbuild command. Why this difference? At any rate, the rpmbuild bb --buildroot to/new/buildrootdir.. does not change the build area for me- 3)The --queryformat command to determine whether my built package is relocatable does not work??? What am I missing or overlooking- I have only built(rpm -bb ...) the package on my Linux box, I have yet to rpm -i it.. does this have anything to do with certain commands not working for me..or is it b/c I'm working as root???? Help:( Also, If I am building a package that was built with RPM 4.03 but delivering it to an enduser with RPM 2.~, what kind of compatibility problems will arise? and vice versa ? does RPM handle this or do I have to explicitly do a workaround for backwards/upward compatibility? suggestions? Thank you for your help, _________________________________________________________________ Join the world’s largest e-mail service with MSN Hotmail. http://www.hotmail.com _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
