#803 Add titles to all language-specific pages.
Merged 10 months ago by ignatenkobrain. Opened 10 months ago by qulogic.
qulogic/packaging-committee lang-titles  into  master

@@ -1,4 +1,4 @@ 

- = Packaging Ada programs and libraries

+ = Ada Packaging Guidelines

  

  This document describes the current policies for packaging Ada programs and libraries for Fedora. These are Ada-specific amendments to the generic Packaging Guidelines. Ada packages must also conform to the Packaging:Guidelines[Packaging Guidelines] and the Packaging:ReviewGuidelines[Review Guidelines].

  

@@ -1,4 +1,4 @@ 

- = C and C++

+ = C and C++ Packaging Guidelines

  // https://github.com/asciidoctor/asciidoctor/commit/426d8389aa1706a589b66c96801542f587ae6b61

  :pp: ++

  

@@ -1,3 +1,5 @@ 

+ = D Packaging Guidelines

+ 

  == ldc

  

  All D packages depend on ldc to build, so every package must have ldc as BuildRequires. In addition, the ldc package includes some useful macros for D packages.

@@ -1,3 +1,5 @@ 

+ = Fortran Packaging Guidelines

+ 

  == Modules and include files

  

  The fortran modules files, ending in .mod are files describing a fortran 90 (and above) module API and ABI. These are not like C header files describing an API, they are compiler dependent and arch dependent, and not easily readable by a human being. They are nevertheless searched for in the includes directories by gfortran (in directories specified with `+-I+`).

@@ -1,3 +1,5 @@ 

+ = Java Packaging Guidelines

+ 

  __TOC__

  

  This page represents Fedora guidelines for packaging libraries and applications written in Java and related languages using Java Virtual Machine as bytecode interpreter. It does not aim to extensively describe packaging techniques and tips. RPM macros and commands used here are documented in man pages. Furthermore a separate https://fedora-java.github.io/howto/latest/[Java Packaging HOWTO] describes Java packaging techniques in detail and includes examples, templates and documentation aimed at packagers and Java developers who are taking their first steps in Java RPM packaging.

@@ -1,3 +1,5 @@ 

+ = JavaScript Packaging Guidelines

+ 

  == Overview

  

  JavaScript code used for the web needs special consideration to ensure that it meets the high standards expected of all code shipped by Fedora, while still being useful and complying with conventions already used on millions of websites. Additionally, certain libraries typically used on the web can also be useful in a server-side context (by nodejs or rubygem-execjs), so it's important to package JavaScript so it meets the standards required of locally executed code as well.

@@ -1,4 +1,4 @@ 

- == Lisp Packaging Guidelines

+ = Lisp Packaging Guidelines

  

  This document seeks to document the conventions and customs surrounding the proper packaging of Common Lisp implementations and libraries in Fedora.

  This document does _not_ describe conventions and customs for application programs that are written in Common Lisp.

@@ -1,3 +1,5 @@ 

+ = Mono Packaging Guidelines

+ 

  __TOC__

  

  == File Locations and Architectures

@@ -1,3 +1,5 @@ 

+ = Node.js Packaging Guidelines

+ 

  == Naming Guidelines

  

  * The name of a Node.js extension/library package must start with _nodejs-_ then the upstream name or name used in the npm registry. For example: _nodejs-foomodule_. While it is uncommon for a package's name to contain _node_, if it does, you should still add the nodejs prefix. For instance, the npm registry contains a _uuid_ and a _node-uuid_ module, which would need to be named _nodejs-uuid_ and _nodejs-node-uuid_, repsectively.

@@ -1,3 +1,5 @@ 

+ = OCaml Packaging Guidelines

+ 

  This document seeks to document the conventions and customs surrounding the proper packaging of ocaml modules in Fedora. It does not intend to cover all situations, but to codify those practices which have served the Fedora ocaml community well.

  

  == Naming

@@ -1,4 +1,4 @@ 

- = How to package Octave packages

+ = Octave Packaging Guidelines

  

  == What is Octave?

  

@@ -1,3 +1,5 @@ 

+ = PHP Packaging Guidelines

+ 

  __TOC__

  

  Fedora Packaging Guidelines for PHP addon modules

@@ -1,3 +1,5 @@ 

+ = Perl Packaging Guidelines

+ 

  __TOC__

  

  == License tag

@@ -1,3 +1,5 @@ 

+ = Python Packaging Guidelines

+ 

  __TOC__

  

  == Python Version Support

@@ -1,3 +1,5 @@ 

+ = R Packaging Guidelines

+ 

  __TOC__

  

  == What is R?

@@ -1,3 +1,5 @@ 

+ = Ruby Packaging Guidelines

+ 

  __TOC__

  

  There are three basic categories of ruby packages: link:#RubyGems[ ruby gems], link:#Non-Gem_Packages[ non-gem ruby packages], and link:#ruby_applications[ applications written in ruby]. These guidelines contain sections common to all of these as well as sections which apply to each one individually. Be sure to read all the guidelines relevant to the type of ruby package you are building.

@@ -1,4 +1,4 @@ 

- = Rust

+ = Rust Packaging Guidelines

  

  This document details best practices for packaging Rust crates. Note that the rust2rpm tool, available as a Fedora package or at https://pagure.io/fedora-rust/rust2rpm, automates many of these steps. It is advisable to try `+rust2rpm $crate+` first before attempting to write a specfile by hand.