Creating and maintaining binary packages

Versioning convention

• plan is to go 0.1 -- 0.2 -- 0.3 etc until we put together a version we proudly call 1.0
• minor bugfix releases are tracked and designated by an additional (third) integer, 0.1.1, 0.1.2 ... 1.0.1 etc.

GNU/Linux

• autopackage format
  • create binaries for Linux that install on any distribution
  • packages come with GUI as well as commandline interface
• Backports: see backports.org
• Debian packages - are being worked on by Andreas Tille
• Ubuntu packages - are being worked on by Sebastian Hilbert
• Mandriva packages - are being worked on by Sebastian Hilbert
• openSUSE packages - are being worked on by Sebastian Hilbert

MS Windows

• NSIS/Nullsoft Installer
  • step by step guide
  • GUI interface - HM NIS Edit
  • Used by many Open Source projects
  • working examples are in Gnumed's CVS already
  • seems like there even is a Linux version of this so you can build MS Windows install routines without ever leaving GNU/LInux

Mac OSX

• step by step guide

All platforms

• BitRock
  • non free - supplies free licenses to developers of FOSS
  • caters for Linux, MacOSX and Windows with same look and feel
  • multiple interfaces GUI/non-GUI

Some hints on how to start:

1) decide which platform you want to target (see above)

2) find out which tool you want to use on that platform (see above / google is your friend)

3) get yourself a snapshot of the source as anonymous user

4) build installer (see above) … a topic TarballContents may help

5) ask on Mailinglist if you need help (e.g. target directories)

6) announce result on Mailinglist

7) party enjoy the praise