On Tue, 16 Oct 2007, Matthew Miller wrote: > On Tue, Oct 16, 2007 at 11:21:16AM -0400, Robert P. J. Day wrote: > > what's the canonical way to build a modified binary rpm from the > > original source rpm? i can download the source rpm, install it under > > my own "rpms/" directory, then run: > > $ rpmbuild -bp <spec file> > > to run the prep stage. > > at that point, i can mess with the source, but it's not clear what > > command to invoke to have the build pick up at that point and finish > > off the build to create the (now modified) binary rpm. > > Mess with the source, generate a patch, and then add it to the spec > file. Add a short string and number to the end of the release tag > (so "Release: 1" becomes "Release 1.rday.1" or similar), and then do > rpmbuild -ba on that. just to clarify that there isn't something i'm missing, let me summarize the steps. first, i can grab the source rpm and "install" it with rpm. that gives me (under my rpm work directory): 1) the spec file 2) the gzipped tarball 3) all the patch files now, i can't start building any patches until i untar the tarball. i can't do that with "rpmbuild -bp" since that not only unzips the tarball, but it applies all the patches. whoops, that's gone too far. so i'm reduced to untarring the tarball manually, creating my patch, adding it to the patch dir with the rest, mod'ding the spec file, and finally running "rpmbuild -bb" on the spec file. is that about right? rday -- ======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA http://crashcourse.ca ======================================================================== _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
