Submitting packages for inclusion in the Salix repository

From Salix OS
Revision as of 08:16, 30 July 2012 by Thenktor (Talk | contribs)

Jump to: navigation, search

Contents

What packages to submit

Feel free to submit packages for any open source software you like. Replacing Slackware packages is generally not accepted, unless there is a really important reason.

You can also package proprietary software, provided re-distribution of that software is allowed (like for example the opera web browser).

When to submit packages

When preparing for the next Salix release, a current repository will be available in the Salix servers, which will be in sync with Slackware's own current repository. A Salix current repository generally appears around the time Slackware's current repository reaches RC1 state. Any packages you submit at that point will be considered for inclusion in the Salix binary repositories. However, there might be cases where the packages will be added to the Salix slkbuild repository instead, depending on the Salix developers' workload.

After a new Salix release is made, the current repository will be taken offline and new packages will no longer be accepted in the Salix binary repositories. Any packages you submit at that point, will only be considered for inclusion in the Salix slkbuild repository. The exclusion to that rule, is if a package is needed for a Salix edition release and it's not already part of the binary repositories; these packages will be considered for inclusion in the Salix binary repositories anyway. You should make sure that any package you submit for inclusion in the Salix slkbuild repository is not already available through slackbuilds.org. If it is, it will only be accepted if there is a really important reason to replace the slackbuilds.org package.

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 ticket system. You will need to have a SourceForge account before you can login and submit a new bug report, or you can use openid to log in to SourceForge instead. 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.

If you would like a more automated way to create the bugreports for submitting packages, have a look at Shador's script at the forums: http://www.salixos.org/forum/viewtopic.php?p=1062#p1062

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.

Retrieved from "https://docs.salixos.org/wiki/index.php?title=Submitting_packages_for_inclusion_in_the_Salix_repository&oldid=3729"