2010-11-04 13:00:43 -04:00
|
|
|
NOTES ON THE EMACS PACKAGE ARCHIVE
|
|
|
|
|
2013-08-29 15:20:42 -04:00
|
|
|
The GNU Emacs package archive, at elpa.gnu.org, is managed using a Git
|
|
|
|
repository named "elpa", hosted on Savannah. To check it out:
|
2011-03-07 19:08:03 -05:00
|
|
|
|
2014-06-16 23:29:08 +02:00
|
|
|
git clone git://git.sv.gnu.org/emacs/elpa
|
2011-03-11 17:53:47 -05:00
|
|
|
cd elpa
|
2014-06-16 23:29:08 +02:00
|
|
|
git remote set-url --push origin git+ssh://git.sv.gnu.org/srv/git/emacs/elpa
|
2011-03-11 17:53:47 -05:00
|
|
|
[create task branch for edits, etc.]
|
2011-03-07 19:08:03 -05:00
|
|
|
|
2013-08-29 15:20:42 -04:00
|
|
|
Changes to this branch propagate to elpa.gnu.org via a "deployment" script run
|
|
|
|
daily. This script (which is kept in elpa/admin/update-archive.sh) generates
|
2017-09-13 15:52:52 -07:00
|
|
|
the content visible at https://elpa.gnu.org/packages.
|
2011-03-07 19:08:03 -05:00
|
|
|
|
2013-08-29 15:20:42 -04:00
|
|
|
A new package is released as soon as the "version number" of that package is
|
2015-09-11 11:04:24 -07:00
|
|
|
changed. So you can use 'elpa' to work on a package without fear of releasing
|
2013-08-29 15:20:42 -04:00
|
|
|
those changes prematurely. And once the code is ready, just bump the
|
|
|
|
version number to make a new release of the package.
|
2011-03-07 19:08:03 -05:00
|
|
|
|
2011-03-11 17:53:47 -05:00
|
|
|
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.
|