diff options
| author | Slack Coder <slackcoder@server.ky> | 2024-03-27 16:07:50 -0500 |
|---|---|---|
| committer | Slack Coder <slackcoder@server.ky> | 2024-03-27 16:41:31 -0500 |
| commit | 365869e1a9f604f3880a4dd4e9b0d9263e057cd7 (patch) | |
| tree | 4e6d359e03bd168d340c38e3af8366171b551913 | |
| parent | ef04462873b369ade9ccd90b764d5e1d45e5f6a2 (diff) | |
| download | slackbuilds-365869e1a9f604f3880a4dd4e9b0d9263e057cd7.tar.xz | |
README: Add note about package tags
| -rw-r--r-- | README.md | 17 |
1 files changed, 11 insertions, 6 deletions
@@ -1,14 +1,19 @@ # Slack Coder's SlackBuilds A collection of [slack build scripts](https://slackbuilds.org/howto/) to build -Slackware packages from application source code. A notable policy difference -here is to use the application's official source code location. - -Not all are my own, are copied from elsewhere with only the download location -and version updated. This will be clear from the copyright notice or build tag -in the SlackBuild script. +Slackware packages from application source code. ## See Also - [Alien Bob's SlackBuilds](http://www.slackware.com/~alien/slackbuilds) - [SlackBuilds.org](https://slackbuilds.org) + +## Package tags + +It is standard for third party slackware packages to be built with a 'tag' +appended to their package name. It helps signal to origin of the package but +there is no hard rule. Check +[linuxquestions](https://www.linuxquestions.org/questions/slackware-14/what-are-slackware-package-tags-4175735243/) +for further discussion. + +These packages are tagged with '_slackcoder'. |