Packaging

Guidelines for making Mercurial binary packages.

This page is intended for developers.

1. Things to note

• Don't enable any extensions by default

• Install contrib/mergetools.hgrc so merge tools work

• Consider packaging the hgweb scripts and relevant items from contrib/
• Run the test suite on your platform
• List your package on the Downloads page

• Keep up with our time-based releases

2. SSL support

Packagers are encouraged to integrate as well as possible with the platforms existing PKI, for example by distributing a hgrc.d/cacert.rc with configuration of web.cacerts. If the platform doesn't have a suitable CA list you might want to distribute your own - for example the one from cURL/Mozilla. See CACertificates.

3. Make nightly builds available

Nightly builds help users give quick feedback on bugfixes. These should generally be made from the tip of the stable branch.

4. Stay in touch

Announcements of releases and code freezes are made on the Mercurial-packaging list.

5. See also

• TimeBasedReleasePlan

• Download

CategoryProject