branch: elpa-admin
commit 04669643891fad9721b8b50fc0caf693e969ec11
Author: Stefan Monnier <[email protected]>
Commit: Stefan Monnier <[email protected]>
* README.org (Adding a package): Adjust to use the new `make` targets
---
README.org | 24 ++++++++++++++----------
1 file changed, 14 insertions(+), 10 deletions(-)
diff --git a/README.org b/README.org
index d64ceff..946cf7b 100644
--- a/README.org
+++ b/README.org
@@ -194,29 +194,33 @@ packages with:
Once it is decided we want to add a package =[PKG]=, here's what it takes:
-- Fetch the upstream code with something like:
+- Add a corresponding entry to the file =externals-list=, then
#+begin_src sh
- git fetch [PKGREMOTE]
+ make fetch/<pkgname>
+ make packages/<pkgname>
+ make build/<pkgname>
#+end_src
- Let's say the code is now in =[PKGBRANCH]=.
+- Make sure the resulting tarball looks good and works well.
-- Push that code to =nongnu.git=:
+- You might also check that it can be compiled in place:
#+begin_src sh
- git push nongnu [PKGBRANCH]:refs/heads/externals/[PKG]
+ make packages/<pkgname>
#+end_src
-- Add a corresponding entry to the file =externals-list=.
+- Push the package's code to =nongnu.git=:
-- Make sure the resulting tarball looks good and works well.
+ #+begin_src sh
+ make sync/<pkgname>
+ #+end_src
-- Commit and push that change:
+- Commit and push the change to =externals-list=:
#+begin_src sh
- git commit -m 'New package [PKG]'
- git push
+ git commit -m "* externals-list (<pkgname>): New package" -- externals-list
+ git push
#+end_src
* License
