On 16 Apr 2004 11:03:06 +0200, Chris Rouch wrote: > > On Fri, 16 Apr 2004 08:09:48 +0000 > Mikhael Goikhman <[EMAIL PROTECTED]> wrote: > > > > Ditto with the ones on rpmfind.. just get the source rpm and compile > > > for your machine... if it compiles on your machine it will > > > definitely run fine! > > > > > > rpmbuild --rebuild blah-foo.src.rpm > > > > This is a bad advice, > > Why is that bad advice?
This advice works in some cases (when you are happy with defaults). But there is a more configurable (and I think convenient) way to do this. > > the good advice is to follow the instructions in: > > > > http://fvwm.org/documentation/dev_creating_rpms.php > > It would be useful to have a link to that from the FAQ, although I think > it's overly complicated. These 3 simple steps work for me: > > 1) Create a ~/.rpmmacros file thus: > > %_topdir /home/user/redhat > > (that's taken from the page you referenced ) I think rpmbuild does not create this directory and its subdirs, so this should be done once too. > 2) download the tarball and put it in /tmp If one uses cvs to update releases or snapshots, then he doesn't need this download step. > 3) run e.g. rpmbuild -tb /tmp/fvwm-2.5.10.tar.gz Then you get fvwm-2.5.10-1 rpm and you have no chance to change the release string, the configure params and the make params. > fvwm already provides a .spec file in the tarball, so IMO it makes > sense to use the facilities rpm provides rather than unpack the > tarball and run configure and make. The provided spec file is ok and may be used as a template. However it is patched by "make rpm-dist" procedure that is the suggested/universal way. I kind of like that users get the release string "0.current-date" by default, and not "1" that usually means final/official rpm release. Regards, Mikhael. -- Visit the official FVWM web page at <URL: http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
