Re: Building an RPM from a compiled application

["Mike A. Harris" <mharris meteng on ca>]

On Tue, 12 Sep 2000, Bill Woodward wrote:

>I'm looking for advice on building an rpm from an existing software
>product that we've ported to Linux.  We have our own installation
>procedure (basically, scripts that untar a tar archive and configure
>some information), and I'm trying to fit it into the rpm scheme.  I'm
>confused as to the best way to do it.
>
>It seems that I could approach it in one of two ways:
>
>1) Create a spec file that builds the source, installs into
>RPM_BUILD_ROOT, and packages up the files.  This seems to be more how
>rpm is expected to work, but it requires us to rework an automated build
>environment, only for Linux (yes, we're not going to ship rpms on other
>platforms)

You can create the .spec file, and in the install section put the
commands that normally install your package.  Then in the %files
section you can capture the filenames and set ownership and
permissions with %defattr, et al.

Most packages do something like this.


>2) Build normally, and just use rpm for the packaging.  This seems to
>make more sense from our build environment, but I can't figure out how
>to do it.  

This is essentially what I just described above.  What is the
normal procedure from source tarball for building your app and
installing it?

./configure
make all
make install

Or something different?  Post how you do it, and we'll see if we
can come up with some suggestions.

TTYL

--
      Mike A. Harris  -  Computer Consultant  -  Capslock Consulting
Linux advocate, Open source advocate | Copyright 2000 all rights reserved
     ================================================================
Want to try a new high performance open source web server?  Try Caudium!
http://caudium.org            http://caudium.sourceforge.net