snailed
/
void-packages
2
0
Fork 0
Code Issues 1 Pull Requests 1 Actions Activity

Manual.md: Add quality requirements (#4025)

This commit is contained in:
Toyam Cox 2016-04-14 02:05:31 -04:00 committed by Juan RP
parent 2841bb7c73
commit e2fe9ef294
1 changed files with 19 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
Manual.md
View File

@ -6,6 +6,7 @@ packages for XBPS, the `Void Linux` native packaging system.
*Table of Contents* *Table of Contents*
* [Introduction](#Introduction) * [Introduction](#Introduction)
* [Quality Requirements](#quality_requirements)
* [Package build phases](#buildphase) * [Package build phases](#buildphase)
* [Package naming conventions](#namingconvention) * [Package naming conventions](#namingconvention)
* [Libraries](#libs) * [Libraries](#libs)
@ -84,6 +85,24 @@ If everything went fine after running
a binary package named `foo-1.0_1.<arch>.xbps` will be generated in the local repository a binary package named `foo-1.0_1.<arch>.xbps` will be generated in the local repository
`hostdir/binpkgs`. `hostdir/binpkgs`.
<a id="quality_requirements"></a>
### Quality Requirements
Follow this list to determine if a piece of software or other technology may be
permitted in the Void Linux repository. Exceptions to the list are possible,
and may be accepted, but are extremely unlikely. If you believe you have an
exception, start a PR and make an argument for why that particular piece of
software, while not meeting the below requirements, is a good candidate for
the Void packages system.
1. System: The software should be installed system-wide, not per-user.
1. Compiled: The software needs to be compiled before being used, even if it is
software that is not needed by the whole system.
1. Required: Another package either within the repository or pending inclusion
requires the package.
<a id="buildphase"></a> <a id="buildphase"></a>
### Package build phases ### Package build phases