When creating autopackages, you will come in contact with some or all of our tools. We provide tools to create the package (makepackage), a wrapper around gcc to produce portable binaries (APBuild), a binary relocation library (BinReloc) and a dlopen/dlsym wrapper (Relaytool) to make it easier to soft link dependencies instead of linking against them. There is also a GUI tool to create the spec-file (mkapspec) which examines your project and creates an .apspec based on what it finds.

All these tools can be downloaded on our download tools page.

We provided documentation ranging from beginner style howtos and tutorial to advanced guides in making shared libraries. Many of our guides are worth the read even if you never intend to create an autopackage.

• Quickstart guide (1 page)
  A quick introduction to creating autopackages.
• Packagers Manual (around 30 pages)
  The complete manual for packagers.
• Tutorial (4 pages)
  Step by step example on building an autopackage
• Autopackage API Reference
  Find out what's available to your scripts.

Articles and more documentation.

We always need people to help us develop and spread the use of Autopackage. Both programmers and non-programmers can help. Here are some areas that we could use some help:

• People who know bash/C to help implement new features.
• People who know packaging (and programming) to create new packages that can then be sent upstream.
• People who know web design to help Linux developers improve their websites.
• People who know Linux, to help us with testing and distro compatibility.
• People who know people, to help politely spread the word.
• People who speak other languages, to help translate Autopackage.

If you want to help, talk to us on the forums, IRC, or the mailing list. We want to hear from you. Thank you!

Resources

• Translations
  Contains resources for translators, including language statistics.
• Source
  How to get the current source code from Autopackage SVN.
• SVN Activity
  See the latest commits in the Autopackage SVN.