rpms/redhat-rpm-config
7
0
Fork 0
Code Issues Pull Requests Releases Activity
c10s
redhat-rpm-config/macros.fedora-misc-srpm

44 lines
1.7 KiB
Plaintext
Raw Permalink Normal View History

clean up macro and lua function documentation
2020-05-29 06:47:28 +00:00
# Fedora macros, safe to use at SRPM build stage
Add a file for miscellaneous macros.
2016-04-12 02:41:45 +00:00
# A directory for rpm macros
%rpmmacrodir /usr/lib/rpm/macros.d
Add %_metainfodir macro. An intervening commit added a fix to %forgeautosetup, but the specfile was not updated. I indicated the fix in the %changelog.
2018-04-20 17:05:38 +00:00
# A directory for appdata metainfo. This has changed between releases so a
# macro is useful.
%_metainfodir %{_datadir}/metainfo
Add %_swidtagdir for directory for SWID tag files describing the installation. Signed-off-by: Jan Pazdziora <jpazdziora@redhat.com>
2018-10-11 09:29:00 +00:00
# A directory for SWID tag files describing the installation
%_swidtagdir %{_prefix}/lib/swidtag/fedoraproject.org
misc: add a wordwrap helper
2018-11-08 18:21:06 +00:00
clean up macro and lua function documentation
2020-05-29 06:47:28 +00:00
# Applies the fedora.wordwrap filter to the content of an rpm variable, and
# prints the result.
# – putting multiple lines of UTF-8 text inside a variable is usually
# accomplished with %{expand:some_text}
# Control variables, flags and arguments:
# -v <variable_name> (default value: _description)
misc: add a wordwrap helper
2018-11-08 18:21:06 +00:00
%wordwrap(v:) %{lua:
local fedora = require "fedora.common"
clean up macro and lua function documentation
2020-05-29 06:47:28 +00:00
local variable = "%{?" .. rpm.expand("%{-v*}%{!-v:_description}") .. "}"
misc: add a wordwrap helper
2018-11-08 18:21:06 +00:00
print(fedora.wordwrap(variable))
}
Add %new_package %new_package is a wrapper around Name: and %package that abstracts their quirks from packagers and macros. Its behavior is controled by the %{source_name} global variable: – when %{source_name} is not set, the first call to %new_package will create a Name: block and set %{source_name} to the %{name} of this block. – when %{source_name} is set: – a call to %new_package with no arguments creates: Name: %{source_name} – otherwise, a call to %new_package creates the corresponding: %package… line, unless the resulting %{name} matches %{source_name}. In that case it creates: Name: %{source_name} as before. Arguments: – -n and %1 like %package – -v to print the variables %new_package sets directly. The intended use-case it to: – simplify coordination between macros that create subpackages, – make it easy for packagers to declare which of the macro-created packages owns the SRPM, and – make %{source_name} available within spec files and not just as a dnf synthetic variable. Unlike %{name} %{source_name} matches the SRPM name regardless of its location within the spec file.
2020-04-21 17:39:15 +00:00
clean up macro and lua function documentation
2020-05-29 06:47:28 +00:00
# A single Name: and %package substitute
# Control variables, flags and arguments:
# %{source_name} the SRPM name
# %{source_summary} the SRPM summary
# %{source_description} the SRPM description
# -n <name> declare a package named <name>
# (%package-like behavior)
# -v be verbose
# %1 declare a package named %{source_name}-%{%1}
# (%package-like behavior)
Add %new_package %new_package is a wrapper around Name: and %package that abstracts their quirks from packagers and macros. Its behavior is controled by the %{source_name} global variable: – when %{source_name} is not set, the first call to %new_package will create a Name: block and set %{source_name} to the %{name} of this block. – when %{source_name} is set: – a call to %new_package with no arguments creates: Name: %{source_name} – otherwise, a call to %new_package creates the corresponding: %package… line, unless the resulting %{name} matches %{source_name}. In that case it creates: Name: %{source_name} as before. Arguments: – -n and %1 like %package – -v to print the variables %new_package sets directly. The intended use-case it to: – simplify coordination between macros that create subpackages, – make it easy for packagers to declare which of the macro-created packages owns the SRPM, and – make %{source_name} available within spec files and not just as a dnf synthetic variable. Unlike %{name} %{source_name} matches the SRPM name regardless of its location within the spec file.
2020-04-21 17:39:15 +00:00
%new_package(n:v) %{lua:
new_package: create basic SRPM header as fallback Make SRPM handover between macros even more graceful and reliable by auto-creating a basic SRPM header before attempting declaration of a different sub-package. With this change things will just work as long as the default %{source_name} %{source_summary} and %{source_description} are set by something to sensible values.
2020-05-20 09:13:02 +00:00
local fedora = require "fedora.common"
local pkg_name = fedora.readflag("n")
local verbose = fedora.hasflag("v")
local name_suffix = fedora.read("1")
local source_name = fedora.read("source_name")
local first = not ( fedora.read("name") or fedora.read("currentname") )
fedora.new_package(source_name, pkg_name, name_suffix, first, verbose)
Add %new_package %new_package is a wrapper around Name: and %package that abstracts their quirks from packagers and macros. Its behavior is controled by the %{source_name} global variable: – when %{source_name} is not set, the first call to %new_package will create a Name: block and set %{source_name} to the %{name} of this block. – when %{source_name} is set: – a call to %new_package with no arguments creates: Name: %{source_name} – otherwise, a call to %new_package creates the corresponding: %package… line, unless the resulting %{name} matches %{source_name}. In that case it creates: Name: %{source_name} as before. Arguments: – -n and %1 like %package – -v to print the variables %new_package sets directly. The intended use-case it to: – simplify coordination between macros that create subpackages, – make it easy for packagers to declare which of the macro-created packages owns the SRPM, and – make %{source_name} available within spec files and not just as a dnf synthetic variable. Unlike %{name} %{source_name} matches the SRPM name regardless of its location within the spec file.
2020-04-21 17:39:15 +00:00
}
Reference in New Issue Copy Permalink