How to build rpm spec files

Just untar a tgz file in a specific location. Or you can generate that list but please avoid that if possible. For example see github. Thanks for all the information. For some reason, when I execute the building of the rpm it seems to seek out Perl dependencies. Again, all I did was compile a Perl distribution using perbrew in a custom location, and after installing all the desired Perl modules using cpanm. I tarred up the folder i. When go to install the RPM it complains of missing Perl dependencies.

Also I have not specified "require" in the spec file. Sign up or log in Sign up using Google. Sign up using Facebook. Hope it helps. Thanks a lot. AutoReqProv: no should be sufficient as no one actually will use that rpm to install the fonts. Just using it to distribute the files via puppet. Registering the fonts will likely be easier with puppet then.

The problem for me is that there are numerous different paths which the. On the machine where the RPM is being installed. I'm only able to determine the specifics by experimenting. As an answer for your edited question, the following might be the answer you seek: Name: test Version: 1. Hope this addresses your question correctly.

Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. This post digs into the spec file, which contains instructions on how to build the RPM.

Again, this article uses fpaste as an example. It is written in Python, and is a one file script. The current version, as the archive shows, is 0. Where these files are installed depends on the Filesystem Hierarchy Standard.

Name , Version , and so on are called tags , and are defined in RPM. The tags to keep an eye out for are:. This section provides general information about fpaste: what it is, which version is being made into an RPM, its license, and so on. If you have fpaste installed, and look at its metadata, you can see this information included in the RPM:.

Next, we start telling RPM what to do. This simply extracts the tar archive into a new folder and keeps it ready for the next section where we build it. You can do more here, like apply patches, modify files for different purposes, and so on.

If you did look at the contents of the source rpm for Python, you would have seen lots of patches there. These are all applied in this section.

So, here we get:. The build section is often the hardest section of the spec, because this is where the software is being built from source. This requires you to know what build system the tool is using, which could be one of many: Autotools, CMake, Meson, Setuptools for Python and so on. Each has its own commands and style. Group is used to categorize the package. Next we have licence which should be included, if for example you are packaging Elasticsearch you should write that corresponding licence in your spec-file.

You can write multiply Source in the specfile like this; Source0, Source1, Source2 and so on. BuildRequires, Requires - BuildRequires is the category you need to list the packages that the software you are packaging requires at build time, whereas Requires is what your rpm requires at runtime.