Zen

Source string Source string

28/10000 · 28

The string is read only.

English Actions
Packaging Tutorial 1: banner
This tutorial demonstrates RPM packaging by packaging the https://github.com/pronovic/banner[banner] program. It is a simple program with a simple https://www.gnu.org/software/automake/manual/html_node/Autotools-Introduction.html[GNU Autotools] build script.
For comprehensive information on how to create RPM files, refer to https://rpm-software-management.github.io/rpm/manual/[RPM Reference Manual]. If you plan to create an RPM package for the Fedora repository, follow the process for xref:Joining_the_Package_Maintainers.adoc[Joining the Package Maintainers], including following the various Fedora guidance.
This tutorial is intended to be run on a Fedora {MAJOROSVER} system. It should, however, work also for other Fedora releases. Just replace strings like `f{MAJOROSVER}` with your release number. Because this tutorial uses Fedora specific features that may not available in other environments, Fedora downstreams such as CentOS Stream or Red Hat Enterprise Linux may or may not work.
The tutorial proceeds in step by step manner, with most steps editing the package's specfile. The final resulting specfile is listed in the end, so in case there is any unclarity how a particular change should be applied, you can peek there.
Installing Packager Tools
Follow xref:Installing_Packager_Tools.adoc[Installing Packager Tools].
Creating the package directory
In Fedora, package build instructions are organized in so called _dist-git_ repositories. There is a separate repository for each package. We mimic this system by creating a new directory for this tutorial. In dist-git, the repository name matches the package name. Fedora's rules for naming packages are written in https://docs.fedoraproject.org/en-US/packaging-guidelines/Naming/[Naming Guidelines]. For banner, package should simply be named `banner`. This is also the name of Fedora's https://packages.fedoraproject.org/pkgs/banner/banner/[official banner package].
$ mkdir banner && cd banner
Inside a Spec File
RPM packages are configured by `.spec` files. Tools such as `rpmdev-newspec` can be used to generate empty specfiles for different purposes. For this tutorial, just create a file called `banner.spec` and paste the following minimal specfile. It does not work yet, but we will try to build it and fix errors as we encounter them.
Name: banner
Version: 1.3.6
Release: %autorelease
Summary: Prints a short string to the console in very large letters
License: GPL-2.0-only
URL: https://github.com/pronovic/banner
Source: https://github.com/pronovic/banner/releases/download/BANNER_V%{version}/banner-%{version}.tar.gz
%description
This is a classic-style banner program similar to the one found in Solaris or
AIX in the late 1990s. It prints a short string to the console in very large
letters.
%prep
%autosetup
%build
%configure
%make_build
%install
%make_install
%files
%changelog
%autochangelog
The specfile starts with a set of _tags_, such as `Name:` and `Version:`, followed by _sections_ such as `%description` and `%prep`. Each tag fits into a single line, whereas each section continues until the next one starts.
Note that, confusingly, in addition to marking the section names, the percent sign `%` also marks RPM _macros_. Thus `%autosetup`, `%configure`, `%make_build`, `%make_install` and `%autochangelog` are not sections.
Tags
`Version` contains the version number of the packaged software.
`Release` numbers specfile updates, package rebuilds and other work within Fedora. The value used here, `%autorelease`, is part of https://docs.pagure.org/fedora-infra.rpmautospec/index.html[rpmautospec], which is https://fedoraproject.org/wiki/Changes/Rpmautospec_by_Default[recommended for Fedora packages]. It ties `Release` to package's Git history. As we do not have a Git repository, `%autorelease` will evaluate to the default value of 1.
Often, `Summary` can be copied from the upstream README. The first letter should be uppercase to avoid `rpmlint` complaints.

Loading…

User avatar None

String added in the repository
$ mkdir banner && cd banner
$ mkdir banner && cd banner
8 months ago
Browse all string changes

Things to check

Multiple failing checks

Following checks are failing:
Unchanged translation: Spanish, Chinese (Simplified Han script)

Reset

Glossary

English English
No related strings found in the glossary.

17802575 String information

Source string description
type: delimited block -
Flags
no-wrap, placeholders:r"`[\w\d -_<>(){}\[\]@$;.\*+=]*`":r"(link:)?https?://[\w\d\-_#?&%=\./@]*":r"xref:[\w\d\-_/]*\.adoc(#[\w\d\-_/]*)?", read-only
Source string location
./pages/Packaging_Tutorial_1_banner.adoc:46
String age
8 months ago
Last updated
8 months ago
Source string age
8 months ago
Translation file
pot/master/pages/Packaging_Tutorial_1_banner.pot, string 10