mirror/emacs
1
0
Fork 0
mirror of https://git.savannah.gnu.org/git/emacs.git synced 2024-11-22 07:09:54 +00:00
Code Issues Releases Activity

admin/notes/elpa: Make Bzr checkout directions more explicit.

Browse Source
This commit is contained in:
Chong Yidong 2011-03-11 17:53:47 -05:00
parent 14239447d3
commit 7f0869bd1d
1 changed files with 16 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
admin/notes/elpa
View File

@ -1,24 +1,24 @@
NOTES ON THE EMACS PACKAGE ARCHIVE
The GNU Emacs package archive, at elpa.gnu.org, is managed using Bzr.
The Bzr branch is hosted on Savannah, and you can check it out with
The GNU Emacs package archive, at elpa.gnu.org, is managed using a Bzr
branch named "elpa", hosted on Savannah. To check it out:
bzr branch bzr+ssh://USER@bzr.savannah.gnu.org/emacs/elpa elpa
cd elpa
echo "public_branch = bzr+ssh://USER@bzr.savannah.gnu.org/emacs/elpa" >> .bzr/branch/branch.conf
bzr bind bzr+ssh://USERNAME@bzr.savannah.gnu.org/emacs/elpa
[create task branch for edits, etc.]
Changes made to this branch propagate to elpa.gnu.org as follows.
Changes to this branch propagate to elpa.gnu.org in a semi-manual way.
There exists a copy of the elpa branch on that machine. Someone with
access must log in, pull the latest changes from Savannah, and run a
"deployment" script that generates the content at the web-visible
location http://elpa.gnu.org/packages.
access logs in, pulls the latest changes from Savannah, and runs a
"deployment" script. This script (which is itself kept in the Bzr
branch) generates the content visible at http://elpa.gnu.org/packages.
The reason things are set up this way, instead of using the package
upload utilities in package-x.el, is so that Emacs hackers can easily
edit the contents of the Savannah "elpa" branch, with the aid of
version control. (For instance, multi-file packages are stored on the
Bzr branch in source form, not as tarfiles.) Because deployment is a
semi-manual process, this allows us some flexibility in making changes
to the branch on Savannah. Furthermore, one can use the elpa branch
to deploy a "local" copy of the package archive, for testing.
The reason we set things up this way, instead of using the package
upload commands in package-x.el, is to let Emacs hackers conveniently
edit the contents of the "elpa" branch. (In particular, multi-file
packages are stored on the branch in source form, not as tarfiles.)
For details on how to use the elpa branch, see that README file in
that branch.
It is easy to use the elpa branch to deploy a "local" copy of the
package archive. For details, see the README file in the elpa branch.