Manual.md: Clarify quality requirements.
This commit is contained in:
parent
2536db0864
commit
70cdd41639
1 changed files with 4 additions and 4 deletions
|
@ -120,11 +120,11 @@ a binary package named `foo-1.0_1.<arch>.xbps` will be generated in the local re
|
||||||
<a id="quality_requirements"></a>
|
<a id="quality_requirements"></a>
|
||||||
### Quality Requirements
|
### Quality Requirements
|
||||||
|
|
||||||
Follow this list to determine if a piece of software or other technology may be
|
To be included in the Void repository, software must meet at least one
|
||||||
permitted in the Void Linux repository. Exceptions to the list are possible,
|
of the following requirements. Exceptions to the list are possible,
|
||||||
and may be accepted, but are extremely unlikely. If you believe you have an
|
and might 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
|
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
|
software, while not meeting any of the following requirements, is a good candidate for
|
||||||
the Void packages system.
|
the Void packages system.
|
||||||
|
|
||||||
1. System: The software should be installed system-wide, not per-user.
|
1. System: The software should be installed system-wide, not per-user.
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue