Difference between revisions of "Submitting packages for inclusion in the Salix repository"
m (→Where to submit packages) |
(bugtracker attachments) |
||
| Line 20: | Line 20: | ||
If the package you are submitting requires any dependencies that are not yet present in the Salix or Slackware repositories, then you will need to submit those dependencies in the same bug report as well. | If the package you are submitting requires any dependencies that are not yet present in the Salix or Slackware repositories, then you will need to submit those dependencies in the same bug report as well. | ||
| − | You will of course need to have some web space to upload all those files. | + | You will of course need to have some web space to upload all those files. If you don't, you can upload all files as attachments to the bugtracker. Alternatively, you can subscribe in the [https://lists.sourceforge.net/lists/listinfo/salix-main Salix-main mailing list] and make a request. You will get an ftp account which you can use to upload your packages. |
| − | + | ||
| − | + | ||
| − | + | ||
| − | If you don't | + | |
== When will my package be included in the repository? == | == When will my package be included in the repository? == | ||
Revision as of 13:58, 23 September 2009
Where to submit packages
If you would like to submit a package for inclusion in the Salix repository, please create a new ticket in our SourceForge bugtracker. You will need to have a SourceForge account before you can login and submit a new bug report. You can set the bug type to:
- package addition, if it is a new package, not previously present in the Salix repository, or
- package upgrade, if it is a new version of a package already present in the Salix repository.
You can also select the Salix version this package is aimed at and also the bug priority, which you can set to a high level if it's an important bugfix or security fix, or to a low level if it's not that urgent to include it in the repository.
What to include in the bug report
When submitting a new package in the bugtracker, please include the following:
- a link to the project's homepage
- link to txz package
- link to md5 checksum
- link to dep file that includes dependency info, if there are any dependencies (you can create one with depfinder). You can skip this file if the package you are submitting has no external dependencies.
- links to all source files you used to create the package. That includes a link to the source tarball(s) you have used as well as links to your Slackbuild, buildscript or SLKBUILD you might have used and generally everything that needs to be present in someone's system so he can recreate the package. Alternatively you can submit an src file that includes links to all of the above mentioned source files. Such an src file will be created when using slkbuild and you have specified the sourcetemplate variable
- link to a package build log. If you're using slkbuild one will be created automatically for you. If you're using a Slackbuild/buildscript, then you can create one when building your package with:
./foo.Slackbuild 2>&1 | tee build-foo.log
If the package you are submitting requires any dependencies that are not yet present in the Salix or Slackware repositories, then you will need to submit those dependencies in the same bug report as well.
You will of course need to have some web space to upload all those files. If you don't, you can upload all files as attachments to the bugtracker. Alternatively, you can subscribe in the Salix-main mailing list and make a request. You will get an ftp account which you can use to upload your packages.
When will my package be included in the repository?
As soon as it gets tested and found to comply with our packaging rules, it will be included in the Salix repository.
