On this page there are .spec files for some software projects;
they might be useful to you if you want to have .rpm and
(.src.rpm) files for the corresponding projects on SuSE.
Of course, these files might also work on other systems, but they are
only tested with SuSE9.2.
The general instructions for all of these .spec files
are as follows:
u -T Name_of_the_downloaded_archive
tbzd -T -X Name_of_the_unpacked_directory
rpmbuild -bs Name_of_the_spec_file
rpmbuild -bb Name_of_the_spec_file
rpmbuild -bb --define "fake 1" Name_of_the_spec_file
A list of some .spec files follows. Please note that
the existence of some .spec file here does not
mean that I am further involved with the corresponding software project.
In particular, I am not the right person to ask questions about these
projects: I only wrote the .spec files to test these projects for
myself, and provide these files to anybody who wants to do the same.
Of course, bug reports about the .spec files are welcome.
The dates always correspond to the last update of the .spec
file - the corresponding versions of the actual projects usually have a
much older date, and meanwhile newer versions of the porject could be
available. It may happen that the .spec file works with older
or newer versions of the project, too, but I usually tested it only with
the mentioned version. If you use a .spec file with a different
version of a project, you should at least edit the version (and release)
numbers in the .spec file correspondingly to avoid confusion.
The following .spec files for the gtkmm2.4 project and related
libraries are for SuSE9.2. They have been written with much care, because
earlier versions of these libraries exist already in SuSE9.2.
These .spec files are written in such a way that they can
be installed parallel (and parallel to the packages of the SuSE9.2
distribution). Therefore, they have strange names like libsigc++2.0
(i.e. 2.0 is part of the name, not part of the
version number and although libsigc++2 exists already in SuSE9.2).
Nevertheless, RPMs requiring e.g.
"libsigc++ >= 1.2" will understand correctly that this
version is installed.
"libsigc++ >= 1.2"
In contrast to the original .spec files of the projects, I have
decided for most of the libraries to put the lengthy documentation into
The original .spec files would have put it into the
-devel packages; this does not appear right to me,
because you do not necessarily need the documentation if you just want
to compile a program which uses the libraries.
To Martin Väth's main download page
Activities on Github
Visit Martin Väth's homepage
List of publications
International research experience
Martin Väth's Homepage at the Czech Academy of Sciences