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