diff options
| author | Stefan Monnier | 2013-08-29 15:20:42 -0400 |
|---|---|---|
| committer | Stefan Monnier | 2013-08-29 15:20:42 -0400 |
| commit | 7763d67c87ae050d4e7cc28f1e0c4b14df037d2e (patch) | |
| tree | c13da3622165115b7e2eb70ea1372f842d2ef243 /admin | |
| parent | 2da4c3ab6f9f2caf026e03c42e74ccd1f1c86c25 (diff) | |
| download | emacs-7763d67c87ae050d4e7cc28f1e0c4b14df037d2e.tar.gz emacs-7763d67c87ae050d4e7cc28f1e0c4b14df037d2e.zip | |
* admin/notes/elpa: Update to the new Git setup.
Diffstat (limited to 'admin')
| -rw-r--r-- | admin/notes/elpa | 25 |
1 files changed, 11 insertions, 14 deletions
diff --git a/admin/notes/elpa b/admin/notes/elpa index db14456fe32..469a0ca8bd1 100644 --- a/admin/notes/elpa +++ b/admin/notes/elpa | |||
| @@ -1,24 +1,21 @@ | |||
| 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 a Bzr | 3 | The GNU Emacs package archive, at elpa.gnu.org, is managed using a Git |
| 4 | branch named "elpa", hosted on Savannah. To check it out: | 4 | repository 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 | git clone git://bzr.sv.gnu.org/emacs/elpa |
| 7 | cd elpa | 7 | cd elpa |
| 8 | echo "public_branch = bzr+ssh://USER@bzr.savannah.gnu.org/emacs/elpa" >> .bzr/branch/branch.conf | 8 | git remote set-url --push origin git+ssh://bzr.sv.gnu.org/srv/git/emacs/elpa |
| 9 | bzr bind bzr+ssh://USERNAME@bzr.savannah.gnu.org/emacs/elpa | ||
| 10 | [create task branch for edits, etc.] | 9 | [create task branch for edits, etc.] |
| 11 | 10 | ||
| 12 | Changes to this branch propagate to elpa.gnu.org in a semi-manual way. | 11 | Changes to this branch propagate to elpa.gnu.org via a "deployment" script run |
| 13 | There exists a copy of the elpa branch on that machine. Someone with | 12 | daily. This script (which is kept in elpa/admin/update-archive.sh) generates |
| 14 | access logs in, pulls the latest changes from Savannah, and runs a | 13 | the content visible at http://elpa.gnu.org/packages. |
| 15 | "deployment" script. This script (which is itself kept in the Bzr | ||
| 16 | branch) generates the content visible at http://elpa.gnu.org/packages. | ||
| 17 | 14 | ||
| 18 | The reason we set things up this way, instead of using the package | 15 | A new package is released as soon as the "version number" of that package is |
| 19 | upload commands in package-x.el, is to let Emacs hackers conveniently | 16 | changed. So you can use `elpa' to work on a package without fear of releasing |
| 20 | edit the contents of the "elpa" branch. (In particular, multi-file | 17 | those changes prematurely. And once the code is ready, just bump the |
| 21 | packages are stored on the branch in source form, not as tarfiles.) | 18 | version number to make a new release of the package. |
| 22 | 19 | ||
| 23 | It is easy to use the elpa branch to deploy a "local" copy of the | 20 | It is easy to use the elpa branch to deploy a "local" copy of the |
| 24 | package archive. For details, see the README file in the elpa branch. | 21 | package archive. For details, see the README file in the elpa branch. |