diff options
| author | Paul Eggert | 2011-03-13 10:28:15 -0700 |
|---|---|---|
| committer | Paul Eggert | 2011-03-13 10:28:15 -0700 |
| commit | 3eca4629203c3038f04db312999ca32d8e292e50 (patch) | |
| tree | 7dab20a2f6de3e300fd266f51b71efd1d9f52188 /admin/notes | |
| parent | 01e0b5adf4e35c2b00705c212b853936fe218cac (diff) | |
| parent | d32df629a23d0e04eb70df9c6e60e821d905c822 (diff) | |
| download | emacs-3eca4629203c3038f04db312999ca32d8e292e50.tar.gz emacs-3eca4629203c3038f04db312999ca32d8e292e50.zip | |
Merge from mainline.
Diffstat (limited to 'admin/notes')
| -rw-r--r-- | admin/notes/elpa | 32 |
1 files changed, 16 insertions, 16 deletions
diff --git a/admin/notes/elpa b/admin/notes/elpa index cbea8cc1dfa..db14456fe32 100644 --- a/admin/notes/elpa +++ b/admin/notes/elpa | |||
| @@ -1,24 +1,24 @@ | |||
| 1 | NOTES ON THE EMACS PACKAGE ARCHIVE | 1 | NOTES ON THE EMACS PACKAGE ARCHIVE |
| 2 | 2 | ||
| 3 | The GNU Emacs package archive, at elpa.gnu.org, is managed using Bzr. | 3 | The GNU Emacs package archive, at elpa.gnu.org, is managed using a Bzr |
| 4 | The Bzr branch is hosted on Savannah, and you can check it out with | 4 | branch named "elpa", hosted on Savannah. To check it out: |
| 5 | 5 | ||
| 6 | bzr branch bzr+ssh://USER@bzr.savannah.gnu.org/emacs/elpa elpa | 6 | bzr branch bzr+ssh://USER@bzr.savannah.gnu.org/emacs/elpa elpa |
| 7 | cd elpa | ||
| 8 | echo "public_branch = bzr+ssh://USER@bzr.savannah.gnu.org/emacs/elpa" >> .bzr/branch/branch.conf | ||
| 9 | bzr bind bzr+ssh://USERNAME@bzr.savannah.gnu.org/emacs/elpa | ||
| 10 | [create task branch for edits, etc.] | ||
| 7 | 11 | ||
| 8 | Changes made to this branch propagate to elpa.gnu.org as follows. | 12 | Changes to this branch propagate to elpa.gnu.org in a semi-manual way. |
| 9 | There exists a copy of the elpa branch on that machine. Someone with | 13 | 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 | 14 | access logs in, pulls the latest changes from Savannah, and runs a |
| 11 | "deployment" script that generates the content at the web-visible | 15 | "deployment" script. This script (which is itself kept in the Bzr |
| 12 | location http://elpa.gnu.org/packages. | 16 | branch) generates the content visible at http://elpa.gnu.org/packages. |
| 13 | 17 | ||
| 14 | The reason things are set up this way, instead of using the package | 18 | The reason we set things up this way, instead of using the package |
| 15 | upload utilities in package-x.el, is so that Emacs hackers can easily | 19 | upload commands in package-x.el, is to let Emacs hackers conveniently |
| 16 | edit the contents of the Savannah "elpa" branch, with the aid of | 20 | edit the contents of the "elpa" branch. (In particular, multi-file |
| 17 | version control. (For instance, multi-file packages are stored on the | 21 | packages are stored on the branch in source form, not as tarfiles.) |
| 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 | 22 | ||
| 23 | For details on how to use the elpa branch, see that README file in | 23 | It is easy to use the elpa branch to deploy a "local" copy of the |
| 24 | that branch. | 24 | package archive. For details, see the README file in the elpa branch. |