SPEC2ARCH.CONF(5)

NAME
spec2arch.conf.conf - Configuration file for spec2arch, which creates ArchLinux PKGBUILD files from RPM spec files

DESCRIPTION

This manual page documents the options that can be set in the spec2arch.conf configuration file. For a description of what spec2arch does, see the spec2arch(8) manpage.

SETTINGS

The syntax of options is OPTION=value - Bash syntax, since it will be sourced by the pkgmake executable, which is written in Bash script.

The following settings are available in spec2arch.conf:

SRC_BASEURL
    Here you can define a base URL where the source is available for download. The string from this setting will be put in front of the source file name defined in the RPM .spec file.

USE_WARNING
    Since the automatic creation of the PKGBUILD file may result in invalid settings and thus need a review, spec2arch can add a warning hint to that fact. You should only ommit it if you are really sure the created PKGBUILD file will be 100% correct. Valid settings are: 0 (no warning) or 1 (default - place a warning).

OVERWRITE_TARGET
    What shall be done if the target PKGBUILD file specified on the command line does already exist - shall it be overwritten without a warning (1), or shall spec2arch better exit with a warning (0 - default)?

BUILD_REPLACE / BUILD_REPLACED
    Replacements to be made in the build() section. The RPM .spec file has some pre-defined variables and conditional scripting which we may need to replace. Since the replace is done using "sed", all statements need to comply to regexp (i.e. escape certain characters). For the replace, we set up two arrays which need to correspond to each other: BUILD_REPLACE holds the strings to be replaced, BUILD_REPLACED the replacement. There are no defaults.

BUILD_REMOVE
    Similiar to above explained BUILD_REPLACE, this is an array of regular expressions describing lines to be completely removed (or, better said: ignored) from the RPM .spec file - i.e. they will not be considered for the PKGBUILD file at all.

DO_BUILD_REPLACE
    Whether we should apply the changes defined by BUILD_REPLACE, BUILD_REPLACED and BUILD_REMOVE (1) or not (0 - default).

EDIT_PKGBUILD
    Shall we invoke the editor after creating the PKGBUILD files to apply manual changes (1, default) or not (0)? Unless you are sure the resulting file will be fine (or adjustments should be done later), you should manually post-process the created PKGBUILD file to make sure it is OK.

EDITOR
    Which editor shall be used (to edit the PKGBUILD file if EDIT_PKGBUILD=1)? By default, spec2arch will use the editor defined by the system variable $EDITOR.

USE_NAMCAP
    If namcap.py is found in the $PATH, shall it be used to verify the generated PKGBUILD file (1 - default) or not (0)? It is recommended to use this tool to detect possible problems.

SEE ALSO

spec2arch(8)

AUTHOR

This manual page was written by Andreas Itzchak Rehberg (devel@izzysoft.de), the author of the program. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 2. More information may be found on the authors website, http://www.izzysoft.de/