Philip Prindeville wrote: > And... what happens if the RPM generates different lists of files based > on the state of the machine it's built on? You should at least know this information. > I.e. what if it auto-detects support libraries (like openssl-devel) that > might unlock additional functionality? > > What if compilation on different processors or different distros changes > the output target package? If you're using the same .spec file on 80 > different machines/releases/processor families, it's hard to believe > that this isn't the case at least occasionally. This all sounds a little bit scary. One of the very useful things about rpm is to get control of the build process to create reproducable builds. Of course rpm is only part of the equation because as you point out the rest of the environment also affects things too. I guess if you don't have control of the environment and don't care then it does not really matter what you put in the rpm file. It will probably be completely different each and every time. :-( I really hate it when things like a 5.97-5.3 to 5.97-5.4 version difference in packages contains massive changes in libraries and dependencies. That basically tells me that there is no quality control in the build process. The careful builders want to know exactly what changed between one package version and another and will try to make sure these are intentional changes and are noted in the package changelogs. Bob _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
