On Fri, Sep 19, 2003 at 01:52:49PM -0400, Alex deVries wrote: > Ferguson, Neale wrote: > >Over the past day or so I've been building things like binutils, gcc, and > >glibc for a 2.6 kernel I've built on s390. One of the problems I encounter > >is something minor may go wrong with a build using "rpm -bb" and the only > >option I have is to fix the problem and start from scratch. I note there's > >a > >--short-circuit option but that is only valid for -bc and -bi. Am I missing > >something obvious? > > I don't think you're missing anything; with large packages like glibc, > the install phase tends to be somewhat lengthy. Using --short-circuit > can save you a *LOT* of time in making sure that your build and install > sections are correct, but it won't actually ever write out an RPM file. > > But there's an upside to this kind of restriction. This ensures that > the RPMs are truly reproducible, and that they didn't require some > manual intervention to get them to build properly.
[ unless something from outside has affected the build process: automatic detection by the configure script is affected by the currently-installed packages, as someone already noted. And you can also cheat and add some outside files, making the whole process totally non-reproducable ] Yes, this is one point where I find deb too lax. > I'm reasonably sure there're some less-documented ways to convince RPM > to go into the RPM file writing phases when using --short-circuit, this > has been a point of controversy for a long time. rpm -bl ? -- Tzafrir Cohen +---------------------------+ http://www.technion.ac.il/~tzafrir/ |vim is a mutt's best friend| mailto:[EMAIL PROTECTED] +---------------------------+
