[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Building RPM from rc4

From: David Summers <david_at_summersoft.fay.ar.us>
Date: 2005-12-10 19:45:47 CET

On Sat, 10 Dec 2005, Kenneth Porter wrote:

> I wanted to try building an RPM from the tarball. In section II.A.2 of
> ./INSTALL is this Note:
>
> Note: For an easy way to generate a new version of the RPM
> source and binary package from the latest source code you
> just checked out, see the packages/rpm/README file for a
> one-line build procedure.
>
> No such one-liner is present.

Ooops, I haven't looked at that for years. Thanks.

Fixed in r17721.

> However, I found that running configure builds Makefiles in the 4 RPM
> package subdirectories that look like they do the Right Thing.
>
> I'm building on Fedora Core 2 and see setups for RH 7 and 8, and RHEL 3
> and 4. I figure I'll try RHEL4 first.
>
> Ideally a single spec file exists in the tarball, so that one can just
> recreate the package from the tarball with "rpmbuild -ta". That requires
> that one use distro detection within the spec file to handle the
> differences. That should also make it easier to maintain the spec files
> and keep the common parts in sync. (RHEL 3 and 4 seem to differ
> primarily in the versioned python directory name, 2.2 versus 2.3. Put
> that in a macro at the top and the rest of the file should be almost
> identical.)

That would be great. Patches greatly welcome, or describe to me how that
could be done and I'll work on it.

> One of the draws of 1.3.0 is that one no longer needs to depend on the
> build host's swig version, but I see build dependencies in the spec
> files for swig and a number of other packages that are now included in
> the tarball. I'd suggest removing those dependencies unless one really
> wants to use the build host's version.
>

I'm not sure I'm following you there. There is a BuildPreReq for swig as
the package builder now has to have swig > 1.3.25, but that is not a
dependency in the generated RPM files.

The way I'm building it does not use the released tarball but generates
the RPMs directly from the Subversion checkout (which is even better
IMHO), so I don't have the neon, apr, apr-util, etc., directories in my
build, they are required to already be installed on the build and target
system.

If there are better ways of doing things I'm always open to that!

    - Thanks

-- 
David Wayne Summers        "Linux: Because reboots are for hardware upgrades!"
david_at_summersoft.fay.ar.us PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt
PGP Key fingerprint =  0B44 B118 85CC F4EC 7021  1ED4 1516 5B78 E320 2001
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Dec 10 19:46:57 2005

This is an archived mail posted to the Subversion Dev mailing list.