Mention elpa branch in admin/notes/BRANCH; clarify admin/notes/elpa.
[bpt/emacs.git] / admin / notes / elpa
CommitLineData
eea682b6
CY
1NOTES ON THE EMACS PACKAGE ARCHIVE
2
eb8694ee
CY
3The GNU Emacs package archive, at elpa.gnu.org, is managed using Bzr.
4The Bzr branch is hosted on Savannah, and you can check it out with
5
6 bzr branch bzr+ssh://USER@bzr.savannah.gnu.org/emacs/elpa elpa
7
8Changes made to this branch propagate to elpa.gnu.org as follows.
9There exists a copy of the elpa branch on that machine. Someone with
10access must log in, pull the latest changes from Savannah, and run a
11"deployment" script that generates the content at the web-visible
12location http://elpa.gnu.org/packages.
13
14The reason things are set up this way, instead of using the package
15upload utilities in package-x.el, is so that Emacs hackers can easily
16edit the contents of the Savannah "elpa" branch, with the aid of
17version control. (For instance, multi-file packages are stored on the
18Bzr branch in source form, not as tarfiles.) Because deployment is a
19semi-manual process, this allows us some flexibility in making changes
20to the branch on Savannah. Furthermore, one can use the elpa branch
21to deploy a "local" copy of the package archive, for testing.
22
23For details on how to use the elpa branch, see that README file in
24that branch.