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

Manual.md: document requirement of tagged release in place linked from PR template

This commit is contained in:
Piotr Wójcik 2021-03-09 20:27:33 +01:00 committed by Piotr
parent 7e44b01da0
commit c7a074aabf
2 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
CONTRIBUTING.md
View File

@ -14,8 +14,6 @@ to build package files from templates.
For this guide, we assume you have basic knowledge about [git](http://git-scm.org), as well as a [GitHub Account](http://github.com). For this guide, we assume you have basic knowledge about [git](http://git-scm.org), as well as a [GitHub Account](http://github.com).
Please note that we do not accept any packages containing non-release versions, such as specific git- or svn-revisions anymore.
To get started, [fork](https://help.github.com/articles/fork-a-repo) the void-linux `void-packages` git repository on GitHub and clone it: To get started, [fork](https://help.github.com/articles/fork-a-repo) the void-linux `void-packages` git repository on GitHub and clone it:
$ git clone git@github.com:<user>/void-packages.git $ git clone git@github.com:<user>/void-packages.git

5
Manual.md
View File

@ -146,6 +146,11 @@ fonts).
Browser forks, including those based on Chromium and Firefox, are generally not Browser forks, including those based on Chromium and Firefox, are generally not
accepted. Such forks require heavy patching, maintenance and hours of build time. accepted. Such forks require heavy patching, maintenance and hours of build time.
Software need to be used in version announced by authors as ready to use by
the general public - usually called releases. Betas, arbitrary VCS revisions,
templates using tip of development branch taken at build time and releases
created by the package maintainer won't be accepted.
<a id="buildphase"></a> <a id="buildphase"></a>
### Package build phases ### Package build phases