branch: elpa-admin
commit 19a11bc8d703dde77f5a165980395b6e948c321b
Author: Eric Abrahamsen <e...@ericabrahamsen.net>
Commit: Eric Abrahamsen <e...@ericabrahamsen.net>
Add explicit instructions for new external packages
* README: Spell out the process for new external packages.
---
README | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/README b/README
index 3223929..48c1059 100644
--- a/README
+++ b/README
@@ -194,6 +194,15 @@ help and only gets in the way.
In the `external' case, the copy of the code is not kept here but in the
`externals/<pkg-name>' branch in the `elpa' repository.
+To add a new externals package, first add this `elpa' repository as a
+new remote in your existing repository. Then push a local branch to a
+new remote branch in `elpa', named externals/<pkgname>. For example:
+
+ git push elpa master:externals/<pkgname>
+
+Then edit the `externals-list' file as mentioned above, and push that
+change to `elpa's master branch.
+
You can check out all the external packages into the `packages' directory
with the command:
