mirror of
https://git.savannah.gnu.org/git/emacs.git
synced 2024-12-02 08:22:22 +00:00
bc511a64f6
Most of this change is to boilerplate commentary such as license URLs. This change was prompted by ftp://ftp.gnu.org's going-away party, planned for November. Change these FTP URLs to https://ftp.gnu.org instead. Make similar changes for URLs to other organizations moving away from FTP. Also, change HTTP to HTTPS for URLs to gnu.org and fsf.org when this works, as this will further help defend against man-in-the-middle attacks (for this part I omitted the MS-DOS and MS-Windows sources and the test tarballs to keep the workload down). HTTPS is not fully working to lists.gnu.org so I left those URLs alone for now.
22 lines
973 B
Plaintext
22 lines
973 B
Plaintext
NOTES ON THE EMACS PACKAGE ARCHIVE
|
|
|
|
The GNU Emacs package archive, at elpa.gnu.org, is managed using a Git
|
|
repository named "elpa", hosted on Savannah. To check it out:
|
|
|
|
git clone git://git.sv.gnu.org/emacs/elpa
|
|
cd elpa
|
|
git remote set-url --push origin git+ssh://git.sv.gnu.org/srv/git/emacs/elpa
|
|
[create task branch for edits, etc.]
|
|
|
|
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
|
|
the content visible at https://elpa.gnu.org/packages.
|
|
|
|
A new package is released as soon as the "version number" of that package is
|
|
changed. So you can use 'elpa' to work on a package without fear of releasing
|
|
those changes prematurely. And once the code is ready, just bump the
|
|
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
|
|
package archive. For details, see the README file in the elpa branch.
|