This is part of The Pile, a partial archive of some open source mailing lists and newsgroups.
Subject: Re: Amaya 2.1 is here. Waiting for the RH rpm From: Steve Borho <sborho@ststech.com> Date: Fri, 25 Jun 1999 10:42:18 -0500 On Thu, Jun 24, 1999 at 11:12:36PM -0500, Benjamin Sher wrote: > Dear friends: > > The W3Consortium Amaya editor/browser 2.1 has just been issued as a tar > ball for Unix/Linux at: > > http://www.w3.org/Amaya/User/BinDist.html > > The earlier 2.0a version is available as an rpm at > http://www.rpmfind.net. I am looking forward to the rpm version of the > new 2.1 Amaya. Any idea as to how long that might take. If anyone knows > of any rpm for Amaya 2.1, could you please let me know? If you wish to graduate permanently from the newbie ranks :^), you can take the final exam: the building of a brand new rpm file. It goes like this: Get the source RPM for 2.0a and install it. This will put a bunch of files in /usr/src/redhat. /usr/src/redhat/SPEC - will have the spec file /usr/src/redhat/SOURCES - will have the tar.gz plus any patches Now, copy the new (2.1) tar file into /usr/src/redhat/SOURCES and then edit the .spec file and make the appropriate changes to indicate the new version number and the new tar file name. You'll probably also want to disable any patches (since they've probably been included in the 2.1 release). Now, try to make it build an RPM: cd /usr/src/redhat/SPEC rpm -ba amaya.spec # Whatever the amaya .spec filename is. This should unpack the tar file into /usr/src/redhat/BUILD, then compile it, then install it into a target area, then create both a binary RPM and a new source RPM. If you go to www.rpm.org, you can get a postscript version of the Maximum RPM book that you can view with gv. It's a good reference to have when you're editing .spec files. === Subject: Re: [HACKERS] --with-mb=SQL_ASCII for 6.5.3 RPMs. From: Lamar Owen <lamar.owen@wgcr.org> Date: Thu, 23 Dec 1999 13:31:58 -0500 Tom Lane wrote: > > Lamar Owen <lamar.owen@wgcr.org> writes: > > (I _know_ that the real fix lies in patching configure.in -- I'm > > just wanting to get the RPM out the door without having to learn how to > > run autoconf first -- unless that would be preferable). > > 1. Install autoconf (get it from any GNU archive). Be sure you have > version 2.13 to ensure you get the same results as the rest of us. > Install is no harder than "configure; make; make install". You do need > to have GNU m4, but if you are on a Linux box you probably already do. > Try "m4 --version" to check. > > 2. type "autoconf" in the pgsql/src directory. > > Can't get much easier. Changing configure.in is a LOT easier than > patching the output, IMHO... Well, I actually have to do both, in the RPM scheme of things. I did as you suggested (RedHat 6.1 ships autoconf 2.13 -- installing is a simple 'rpm -i autoconf-2.13-5.i386.rpm'). Popped configure.in into vi, made the change, ran autoconf, generated the resulting patchset (the RPM philosophy is that a source RPM contains everything necessary to rebuild all the binary RPMs -- using pristine sources plus whatever scripts, patches, and extra programs are necessary to make it build binaries that will run. The control file that determines how to do all of this is called a 'spec' file -- the postgresql spec file is one of the more complex ones due to the large differences in file locations vis-a-vis the pristine source install.), built a test RPM set, and am editing the README now to reflect the successful changes. I should release in a couple of hours, once I have all four sets of binaries built (RH 6.1, RH 6.1 non-locale, RH5.2, RH 5.2 non-locale). ===