Commit 7763d67c authored by Stefan Monnier's avatar Stefan Monnier

* admin/notes/elpa: Update to the new Git setup.

parent 2da4c3ab
NOTES ON THE EMACS PACKAGE ARCHIVE NOTES ON THE EMACS PACKAGE ARCHIVE
The GNU Emacs package archive, at elpa.gnu.org, is managed using a Bzr The GNU Emacs package archive, at elpa.gnu.org, is managed using a Git
branch named "elpa", hosted on Savannah. To check it out: repository named "elpa", hosted on Savannah. To check it out:
bzr branch bzr+ssh://USER@bzr.savannah.gnu.org/emacs/elpa elpa git clone git://bzr.sv.gnu.org/emacs/elpa
cd elpa cd elpa
echo "public_branch = bzr+ssh://USER@bzr.savannah.gnu.org/emacs/elpa" >> .bzr/branch/branch.conf git remote set-url --push origin git+ssh://bzr.sv.gnu.org/srv/git/emacs/elpa
bzr bind bzr+ssh://USERNAME@bzr.savannah.gnu.org/emacs/elpa
[create task branch for edits, etc.] [create task branch for edits, etc.]
Changes to this branch propagate to elpa.gnu.org in a semi-manual way. Changes to this branch propagate to elpa.gnu.org via a "deployment" script run
There exists a copy of the elpa branch on that machine. Someone with daily. This script (which is kept in elpa/admin/update-archive.sh) generates
access logs in, pulls the latest changes from Savannah, and runs a the content visible at http://elpa.gnu.org/packages.
"deployment" script. This script (which is itself kept in the Bzr
branch) generates the content visible at http://elpa.gnu.org/packages.
The reason we set things up this way, instead of using the package A new package is released as soon as the "version number" of that package is
upload commands in package-x.el, is to let Emacs hackers conveniently changed. So you can use `elpa' to work on a package without fear of releasing
edit the contents of the "elpa" branch. (In particular, multi-file those changes prematurely. And once the code is ready, just bump the
packages are stored on the branch in source form, not as tarfiles.) version number to make a new release of the package.
It is easy to use the elpa branch to deploy a "local" copy of the 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. package archive. For details, see the README file in the elpa branch.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment