Rpm spec file user input

At the same time, to keep the. These macros apply only if you have the file listing inside the. I highly recommend including the files directly in the. In this instance, every file in that directory and in any subdirectories will be flagged as documentation. If there are any files in this directory that you want included, you must manually specify them in the file list.

This is useful if you need to create a directory that may not contain files during the installation phase but needs to exist for the program to write to and operate correctly for logs or system information, for example.

Pre- and post-install scripts In some cases, you may need to execute scripts before and after the installation of a particular package—and possibly before and after the removal of the same package. There are a number of reasons why this might be necessary.

One of them is installing programs with new libraries. When a new library is installed on your system, you need to run ldconfig , and you also need to run it when you remove the library to keep the library information on your Linux system current.

For instances like these, you can include a few useful scripts in your RPM package. This helps identify what changes have been made to the RPM package for other users. It should list changes made to the. Although not mandatory for other distributions, it gives anyone looking at the. Finally I found it myself. You can use like this and it worked fine 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. The Overflow Blog. Podcast Making Agile work for data science. Here's what you put in your. 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. The Overflow Blog. Podcast Making Agile work for data science. Stack Gives Back Featured on Meta. For the License tag, fill in the appropriate license for the software.

In the Source tag, fill in the URL of the source archive for the package:. Edit the BuildRequires tag with requirements that are needed to build the package. BuildRequires can contain either a list of required packages or files.

For example, the eject package requires the gettext and libtool packages:. It is recommended to add a list of requirements that this package depends on to the Requires tag.

Requires can contain either a list of required packages or files. In many cases, however, rpmbuild is able to detect the dependencies automatically for you so that you do not need to add them manually.