From: Shortt, K. <KS...@az...> - 2004-08-03 17:06:34
|
David, Your idea for Mike is a great one. If I do this, can I offer my rpm as a submission to the Toolbox for others to benefit from? (ala...Steve Christensen does this at www.sunfreeware.com with Solaris Packages) Opening this channel could make the Toolbox bigger and stronger for those using and depending on it. -k David Clissold wrote: > On Mon, Aug 02, 2004 at 03:29:36PM -0500, Mike wrote: >> I can build these things, but I like the idea of the *.rpm to keep >> separate those things that come as part of the BOS and those things >> that I've added on. The differences between installp and rpm do that >> nicely. > > Mike -- want to try an experiment? > > Suppose that you want a package which is not in the Toolbox, but you > find that it is pre-built at the UCLA site. Their image is just a > compressed tarball, and you'd rather it be in rpm format, but you > also aren't particularly excited about building it yourself. > > So -- how about converting their tarball into an installable rpm > image without actually building anything? You could do this without > really having to know much about rpm builds, using the file below. > > Visit http://aixpdslib.seas.ucla.edu and find the package you want, > then download it. Save the file below (and edit it if a different > package is desired). Then run: "rpm -bb net-snmp.spec" assuming > net-snmp.spec is the name of the saved file. Conventionally you'd > put this file in /opt/freeware/src/packages/SPECS, but you could > store it anywhere. > > This method ought to work with pretty much any of the UCLA images. > Note that theirs are built based in /usr/local, so if you use that > directory for your own other uses, take care that you don't overwrite > any of your own files that you might have copied there. If this is a > concern, list the files in the package (rpm -qlp <rpmname>) after you > create the package but before you install it. |