|
Size: 1250
Comment: unbreak link
|
Size: 1411
Comment: Some linking and emphasis on hgweb scripts.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 12: | Line 12: |
| * Consider packaging the hgweb scripts and relevant items from contrib/ | * Consider packaging the hgweb scripts (to help users [[PublishingRepositories|publish repositories]] without having to download the scripts separately) * Consider packaging relevant items from the `contrib` directory |
| Line 14: | Line 15: |
| * List your package on the Downloads page | * List your package on the [[Download|downloads]] page |
Packaging
Guidelines for making Mercurial binary packages.
![/!\](/moin-static/modernized/img/alert.png "/!\"){kind=small}
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 (to help users publish repositories without having to download the scripts separately)
Consider packaging relevant items from the contrib directory
- 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.