GNOME Bugzilla – Bug 97659
Need .spec file to make it possible for users to create RPMs
Last modified: 2004-12-22 21:47:04 UTC
The gtkmm2 tarball needs a gtkmm2.spec file. The purpose of this file is to make it easy for people to build their own RPMs so they can install gtkmm within the distributions packaging system. Murray, I hope you can attach the .spec file(s) you have received to this bug. Then I'm ready to put in my comments and create a patch against CVS.
This is relevant: http://www.advogato.org/article/573.html Here is the spec file and build patch from Gary Peck <gbpeck@sbcglobal.net>. If only people would stop emailing me directly.
Created attachment 12038 [details] gtkmm2.spec
Created attachment 12039 [details] gtkmm2spec.patch
Created attachment 12043 [details] [review] Patch against CVS to add spec file.
The patch I just added, patches gtkmm.spec.in. I just changed so that the version number is automatically inserted by automake (@VERSION@). It also incorporates the the gtkmm2spec.patch that you added. I vote for committing it to CVS, because it's functional on Red Hat systems. However; Leave this bug open - because there is a "minor" bug. The BuildRequires lines only matches the package names which Red Hat uses. While Red Hat uses e.g. "gtk2-devel", Mandrake uses "libgtk+2.0_0" as package name for GTK+2. This means that you can never satisfy the build dependencies on Mandrake. I looked and asked around, but it seems that it isn't possible to add a "OR" dependency in the BuildRequires. Does anyone have a solution for this problem? If no sensible solution is found, I think the BuildRequires lines should just be removed..
Applied. Thanks. Surely this dependency problems happens for every RPMS that needs GTK+. If there is no general solution then it's OK with me to just support RedHat.