Learn more. Asked 6 years, 4 months ago. Active 6 years, 3 months ago. Viewed 4k times. Improve this question. Thomas Dickey Aleksandr Kostyrev Aleksandr Kostyrev 73 1 1 gold badge 2 2 silver badges 4 4 bronze badges. Add a comment. Active Oldest Votes. Your syntax is off. The test can be evaluated based on the existence of a macro, like:.
Conditionals may be nested within other conditionals. The Name tag contains the proper name of the package. The version string consists of alphanumeric characters, and can optionally be segmented with separators. Optional numerical value which can be used to override normal version-release sorting order.
Used to declare source s used to build the package. All sources will will be packaged into source rpms. Arbitrary number of sources may be declared, for example:.
Used to declare patches applied on top of sources. All patches declared will be packaged into source rpms. Files ending in. Both directives use the named source or patch file to build the resulting binary RPM package as usual, but they are not included in the source RPM package.
The original intent of this ability of RPM was to allow proprietary or non-distributable software to be built using RPM, but to keep the proprietary or non-distributable parts out of the resulting source RPM package, so that they would not get distributed. Rarely used in specs, typically filled in by buildsystem macros.
Control per-package automatic dependency generation for provides and requires. Autoreqprov is equal to specifying Autoreq and Autoprov separately. The following tags are used to supply package dependency information, all follow the same basic form.
Can appear multiple times in the spec, multiple values accepted, a single value is of the form capability [operator version]. Capability names must start with alphanumerics or underscore. Capabilities this package requires to function at all. After the dummy build, you must re-edit your. 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. Marasco 5, 3 3 gold badges 23 23 silver badges 38 38 bronze badges. Chris Maes Chris Maes OP said "during the rpm installation" which isn't possible. Marasco you are correct; I corrected my answer and you have my upvote : — Chris Maes. AkshathaRamesh if your question is answered, then please consider accepting any of these answers to mark your question as solved.
You can optionally upvote other usefull answers. 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.
0コメント