| 1 | NOTES ON THE EMACS PACKAGE ARCHIVE |
| 2 | |
| 3 | The GNU Emacs package archive, at elpa.gnu.org, is managed using a Git |
| 4 | repository named "elpa", hosted on Savannah. To check it out: |
| 5 | |
| 6 | git clone git://bzr.sv.gnu.org/emacs/elpa |
| 7 | cd elpa |
| 8 | git remote set-url --push origin git+ssh://bzr.sv.gnu.org/srv/git/emacs/elpa |
| 9 | [create task branch for edits, etc.] |
| 10 | |
| 11 | Changes to this branch propagate to elpa.gnu.org via a "deployment" script run |
| 12 | daily. This script (which is kept in elpa/admin/update-archive.sh) generates |
| 13 | the content visible at http://elpa.gnu.org/packages. |
| 14 | |
| 15 | A new package is released as soon as the "version number" of that package is |
| 16 | changed. So you can use `elpa' to work on a package without fear of releasing |
| 17 | those changes prematurely. And once the code is ready, just bump the |
| 18 | version number to make a new release of the package. |
| 19 | |
| 20 | It is easy to use the elpa branch to deploy a "local" copy of the |
| 21 | package archive. For details, see the README file in the elpa branch. |