= Ada Packaging Guidelines

  :last-reviewed: 2019-04-04

  This document describes the current policies for packaging

  Ada programs and libraries for Fedora.

  = Alternatives

  :last-reviewed: 2019-04-04

  Alternatives provide means for parallel installation of packages

  which provide the same functionality by maintaining sets of symlinks

  = Ansible Collection Packaging Guidelines

  :last-reviewed: 2022-09-25

  == Forward

  = Packaging Guidelines for AppData Files

  :last-reviewed: 2021-01-18

  If a package contains a GUI application,

  then it SHOULD install a `+.metainfo.xml+` file

  = Automatic Filtering of Provides and Requires

  :last-reviewed: 2019-04-04

  == Summary

  = Linear Algebra Libraries

  == Introduction

  :last-reviewed: 2020-07-18

  = CMake Packaging Guidelines

  This document provides best practices for the usage of

  https://cmake.org/[the CMake build system]

  = Default Services

  == What is a Service?

  = Fonts

  == Foreword

  = GAP Packaging Guidelines

  This document describes the conventions and customs surrounding the proper packaging of https://gap-system.org/[GAP] add-on packages in Fedora. Throughout this document, we use the word _add-on_ to substitute for GAP upstream's use of the word _package_, to avoid confusion with RPM packages.

  = Golang Packaging Guidelines

  :last-reviewed: 2019-06-19

  This document details best practices for packaging Golang packages. Most of it

  is automated by an extensive use of macros.

  = Advanced uses cases

  :last-reviewed: 2019-06-19

  == Shipping additional files

  = Additional annotated templates

  :last-reviewed: 2019-03-22

  == Minimal source package

  = Java Packaging Guidelines

  :last-reviewed: 2022-07-01

  This page represents Fedora guidelines

  for packaging libraries and applications

  = Meson Packaging Guidelines

  This document provides best practices for the usage of https://mesonbuild.com/[the Meson build system] in Fedora packages. Meson is a build system (similar to automake) which can generate code for other lower-level build systems. For example, it can generate code for https://ninja-build.org/[ninja]. When packaging software which builds using Meson it's important to use the `+%meson+` macros instead of `+%ninja+` or other lower-level build system macros directly. The backend used by Meson could change.

  = Packaging Guidelines for MinGW Cross Compilers

  == Introduction

  = Mono Packaging Guidelines

  == File Locations and Architectures

  = Naming Guidelines

  [NOTE]

  .Versioning guidelines have moved

  = PHP Packaging Guidelines

  Fedora Packaging Guidelines for PHP addon modules

  In the Fedora.next world, we have a set of curated Fedora Products as well as the availability of classic Fedora. Historically, we have maintained a single set of configuration defaults for all Fedora installs, but different target use-cases have different needs. The goal of this document is to set out the guidelines for creating per-Product configuration defaults.

  We want to ensure that all packages have sensible defaults for whichever Product on which they are installed, while also avoiding situations where users would have some packages installed with one Product's defaults and some packages with another.

  = Perl Packaging Guidelines

  == License tag

  = PKCS#11 / Smart-Card Support Guidelines

  These guidelines are relevant to maintainers of packages with smart cards drivers (PKCS#11 modules), or smart card related tooling. Its purpose is to bring a consistency in smart card handling on the OS; for background and motivation see the https://fedoraproject.org/wiki/User:Nmav/Pkcs11Status[current status of PKCS#11 in Fedora].

  = Python Packaging Guidelines

  :last-reviewed: 2021-06-04

  ////

  = Python Packaging Guidelines (201x-era)

  :last-reviewed: 2020-08-05

  [IMPORTANT]

  ====

  = Additional Python Guidelines

  :last-reviewed: 2020-01-01

  Here are some additional Python-related guidelines, moved here in order to keep the main page manageable.

  = R Packaging Guidelines

  == What is R?

  = Ruby Packaging Guidelines

  NOTE: *JRuby Gems*:

  Although Fedora has fully functioning JRuby

  = Certificate Handling Guidelines

  These guidelines are relevant to maintainers of packages which utilize smart cards for loading certificate or private key. Its purpose is to bring a consistency in smart card handling on the OS; for background and motivation see the link:https://fedoraproject.org/wiki/User:Nmav/Pkcs11Status[current status of PKCS#11 in Fedora].

  = Scriptlets

  RPM spec files have several sections

  which allow packages to run code on installation and removal.

  = Fedora systemd Services

  This document describes the guidelines for systemd services,

  for use and inclusion in Fedora packages.

  = Tmpfiles.d

  == Overview

  include::{partialsdir}/versions.adoc[]

  = Versioning Guidelines

  Fedora's package versioning scheme

  encompasses both the `+Version:+`

  = Deprecating Packages

  Sometimes a package is intended to be https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/[removed from Fedora], but it is kept in Fedora for some additional (often indeterminate) time for various reasons including maintaining backwards compatibility. In order to prevent new packages from depending on such a package, it can be marked as *deprecated*.

  :packaging-committee: https://pagure.io/packaging-committee[Fedora Packaging Committee]

  :scl-guidelines: https://fedoraproject.org/wiki/User:Toshio/SCL_Guidelines_(draft)[Software Collections]

  :updates-policy: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/[Updates Policy]

  The Packaging Guidelines are a collection of common issues

  and the severity that should be placed on them.

  Report issues with these guidelines, including typos,

  https://pagure.io/packaging-committee[here].

  == Applicability

  In general,

  :packaging-committee: https://fedoraproject.org/wiki/Packaging_Committee[Packaging Committee]

  :legal-team: https://fedoraproject.org/wiki/Legal:Main[Legal Team]

  :kernel-team: https://fedoraproject.org/wiki/Kernel[Kernel Team]

  Not everything can be packaged in Fedora. Most things considered to be "free software" or "open source software" are permitted, but definitions of these are not always consistent and Fedora has a few specific requirements and exceptions. This is an overview of some specific requirements and exceptions, but it is not intended to be exhaustive. If questions arise, the {packaging-committee} and the {legal-team} are the primary places to receive answers.