Re: Building RPMs from CVS

[James Henstridge <james daa com au>]

It is probably easier to go into the package directory, configure it with
autogen.sh, then run "make dist" to produce a distribution tarball that
you can then run "rpm -ta" on.

Personally I use some scripts that allow me to build RPMs from the result
of "make install prefix=/tmp/whatever-root/prefix", as this allows make to
do its job, and not have to rebuild everything every time.  Some of the
scripts are a bit hackish, but if you want them, email me directly.

James Henstridge.

--
Email: james@daa.com.au
WWW:   http://www.daa.com.au/~james/


On Thu, 8 Apr 1999, Jason Tackaberry wrote:

> I'm wondering what's the most straight forward way of building RPMs from
> the CVS source?  What I've been doing is renaming the directory to
> package-version, making a package-version.tar.gz, and then running
> rpm -tb package-version.tar.gz.  This works (with a couple exceptions, see
> below) but it seems to me like there should be an easier way.
> 
> Now I seem to have problems with this method for glib and gtk+.  The only
> difference I can see is that glib and gtk+ build devel packages too.  But
> for glib, for example, it stops with no error:
> 
> Prereqs: /sbin/ldconfig
> 
> Processing files: glib-devel
> Finding provides...
> Finding requires...
> Requires: /bin/sh
> 
> ... and no RPMs are built ...  Any suggestions?
> 
> Jason.
> 
> 
> -- 
>         FAQ: Frequently-Asked Questions at http://www.gnome.org/gnomefaq
>          To unsubscribe: mail gnome-list-request@gnome.org with 
>                        "unsubscribe" as the Subject.
>