khronosschoty
624aa416d5
Repo initialization
|
il y a 4 ans | |
|---|---|---|
| .. | ||
| README | il y a 4 ans | |
| autotools-template.SlackBuild | il y a 4 ans | |
| cmake-template.SlackBuild | il y a 4 ans | |
| doinst.sh | il y a 4 ans | |
| haskell-template.SlackBuild | il y a 4 ans | |
| meson-template.SlackBuild | il y a 4 ans | |
| perl-template.SlackBuild | il y a 4 ans | |
| python-template.SlackBuild | il y a 4 ans | |
| rubygem-template.SlackBuild | il y a 4 ans | |
| slack-desc | il y a 4 ans | |
| template.info | il y a 4 ans | |
README
README is used to display a short description of the application and
any additional instructions on how to build or use the package. You
may list optional dependencies needed to enable additional features.
Some common rules for the README file:
- Maximum of 72 characters per line
- Use 2-4 spaces for indentation, avoid TAB characters
- Plain ASCII or Unicode (UTF-8) are preferred encodings.
- Do not include the homepage URL
- Additional notes before building:
* user/group creation along with correct UID/GID
* strict dependency build order if necessary
* conflicts with any stock Slackware packages
If longer instructions are necessary, place them in a README.SBo file.
any additional instructions on how to build or use the package. You
may list optional dependencies needed to enable additional features.
Some common rules for the README file:
- Maximum of 72 characters per line
- Use 2-4 spaces for indentation, avoid TAB characters
- Plain ASCII or Unicode (UTF-8) are preferred encodings.
- Do not include the homepage URL
- Additional notes before building:
* user/group creation along with correct UID/GID
* strict dependency build order if necessary
* conflicts with any stock Slackware packages
If longer instructions are necessary, place them in a README.SBo file.