leetNightshade
/
help-center-docs
Archived
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Change language of 2-distro section on Package Inclusion Policy to clarify that it is a waiver, not rule.

This commit is contained in:
Joshua Strobl 2017-06-02 17:32:51 +03:00
parent 3fae3981aa
commit cceb4558c8
No known key found for this signature in database
GPG Key ID: 3F6FD9A6B13E584D
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
packaging/package-inclusion-policy/en.md
View File

@ -5,7 +5,7 @@ title = "Package Inclusion Policy"
This policy sets forth the criteria for a package to be accepted for inclusion into the Solus repositories. This policy sets forth the criteria for a package to be accepted for inclusion into the Solus repositories.
- 2-Distro Rule: - 2-Distro Waiver:
- If the software appears in Debian and/or Ubuntu, Fedora, and openSUSE, in the **currently active, core** repositories, the maintainer is permitted to waive some entry requirements (This does not apply to software license, legality or known-insecure software. Additionally this cannot be used to bypass the server rules.). PPAs, OBS projects outside of the **openSUSE**: namespace, or Arch Linux, do **NOT** add any weight to a request. - If the software appears in Debian and/or Ubuntu, Fedora, and openSUSE, in the **currently active, core** repositories, the maintainer is permitted to waive some entry requirements (This does not apply to software license, legality or known-insecure software. Additionally this cannot be used to bypass the server rules.). PPAs, OBS projects outside of the **openSUSE**: namespace, or Arch Linux, do **NOT** add any weight to a request.
- Software Age: - Software Age:
- DOA (dead-on-arrival) packages are generally rejected from Solus. However, they may be included at the discretion of the project, if they provide unique functionality. In addition, this software **MUST** comply with the - DOA (dead-on-arrival) packages are generally rejected from Solus. However, they may be included at the discretion of the project, if they provide unique functionality. In addition, this software **MUST** comply with the