I had short discussion over at Nahant list about RPM cookies. There was this one person (Jos Vos) who claimed that the only "right" way of generating binary packages is using the "--rebuild" option, so that cookie in the SRPM would match a cookie in binary packages for all architectures/distributions particular SRPM was used on. Basically telling me that the way I was building packages (using -bb option) is not the way RPM system was designed to be used (there's no cookie to relate binary package to the source package). Now this sounded a bit odd to me. So I checked how the things are with the RPM packages released by Fedora Project (which is under Red Hat's wing). What I found was that cookies in SRPM and RPM packages do not match (they match for x86_64, for i386 they are different). OK, Fedora Project is not building them using --rebuild option (probably -ba, since there's a cookie in each RPM). So.... After some pondering, I said to myself, maybe better to ask somewhere were RPM gurus hang out. Was I doing something wrong all this time (using -bb option)? Is there actually any use for the cookies? Is anybody actually using them for anything? ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
