Changes between Version 60 and Version 61 of RpmHowToPackagers

Timestamp:

Mar 29, 2017, 12:37:30 PM (8 years ago)

Author:

Silvan Scherrer

Comment:

--

RpmHowToPackagers

@@ -183 +183 @@
 Note that you should not worry too much about the network speed and traffic issues when using these macros since the sources are downloaded only once for each given repository revision; any subsequent attempt to build a package form the same revision will simply use the source ZIP created when the revision is fetched for the first time w/o involving any network connection. This ZIP is also stored in a SRPM file as usual, so a rebuild of the package may be done without accessing the repository as long as the SRPM file for the given set of packages is available. There is also a possibility to use local working copies to fetch the sources from instead of online repositories (see below).
 
-==== %scm_source ====
+=== %scm_source ===
 
 This macro is intended as a replacement for the standard `Source:` tag. The format is as follows:
@@ -191 +191 @@
 where SCM is the type of the source code management system (currently supported ones are `svn`, `git` and `github`), URL is the full URL of the source code repository for the given program and REV is the revision to use.
 
-==== %scm_setup ====
+=== %scm_setup ===
 
 This macro is intended as a replacement for the standard `%setup` macro that starts a `%prep` section.
@@ -352 +352 @@
 Given a package named `package`, the following steps need to be done in order to generate legacy runtime packages with `rpmbuild-bot.sh`:
 
-==== 1. Add a rpmbuild-bot configuration entry ====
+=== 1. Add a rpmbuild-bot configuration entry ===
 
 Add an entry named `RPMBUILD_BOT_LEGACY_package` to `rpmbuild-bot-env.sh` containing a package specification string in the following format:
@@ -364 +364 @@
 Note that `rpmbuild-bot` will properly handle all supported target platforms (as specified in `RPMBUILD_BOT_ARCH_LIST`) when extracting old runtime DLLs in order to make sure that the automatically generated legacy sub-package will carry a DLL built for the same target platform as the main package. If an old version of the DLL didn't exist for this platform, `rpmbuild-bot` will fail. In such a case you should force a specific platform of the old DLL to be used for all target platforms of the new package by using an optional ARCH field in the legacy package specification string.
 
-==== 2. Add a magic macro to package.spec ====
+=== 2. Add a magic macro to package.spec ===
 
 Add a `%legacy_runtime_packages` macro somewhere before the `%prep` section of the .spec file. This will cause `rpmbuild` to create a sub-package named `package-legacy-ABI` for each ABI listed in the configuration variable for this package. There are a few things to note about the generated legacy sub-packages and `%legacy_runtime_packages` specifics: