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

Building RPM from rc4

From: Kenneth Porter <shiva_at_sewingwitch.com>
Date: 2005-12-10 02:27:03 CET

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.

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

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.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Dec 10 03:33:13 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.