You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Heinz Wiesinger 138a180b52 python-template.SlackBuild: Add build instructions for PEP 517/PEP 660 based projects 9 months ago
README README: Add Unicode (UTF-8) encoding as alternative. 6 years ago
autotools-template.SlackBuild autotools-template.SlackBuild: Don't ship .la files 1 year ago
cmake-template.SlackBuild cmake-template.SlackBuild: Don't ship .la files 1 year ago
doinst.sh doinst.sh: Remove double install warning 1 year ago
douninst.sh Added douninst.sh. 1 year ago
haskell-template.SlackBuild *.SlackBuild: Support $PRINT_PACKAGE_NAME env var 1 year ago
meson-template.SlackBuild meson-template.SlackBuild: Support alternative ninja implementations 1 year ago
perl-template.SlackBuild *.SlackBuild: Support $PRINT_PACKAGE_NAME env var 1 year ago
python-template.SlackBuild python-template.SlackBuild: Add build instructions for PEP 517/PEP 660 based projects 9 months ago
rubygem-template.SlackBuild *.SlackBuild: Support $PRINT_PACKAGE_NAME env var 1 year ago
slack-desc slack-desc: OCD tweakage 10 years ago
template.info template.info: Remove APPROVED line 10 years ago

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.