Re: [ELPA] Package proposal: EBDB

[Eric Abrahamsen <eric@ericabrahamsen.net>]

[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> Okay, this is what I was confused about. I have to populate the branch
>> with the code from the existing github repo, obviously I'm not just
>> copying files in there, I need to clone the repo into it somehow. The
>> README says:
>
>> git clone --reference .. --single-branch --branch externals/PACKAGE $(git
>> config remote.origin.url) PACKAGE
>
>> Though I can't tell from the README if that's meant to be the command to
>> add an external to ELPA, or just pull down an existing external and look
>> at it. Anyway, running that command just gets me:
>
> "git clone" doesn't modify any existing repository, so that can't be the
> command that adds a branch to a repository.
>
>> How do I populate the branch?
>
> IIRC it's something like
>
>     git push gnuelpa master:externals/ebdb
>
> assuming you've configured your local clone of ebdb with something like
>
>     git remote add gnuelpa <user>@git.sv.gnu.org:/srv/git/emacs/elpa.git

Aha! Thank you, that's what I was missing. It seems to have worked, I
guess I'll know for sure when the package gets built.

Assuming all goes well, can I push this documentation patch to ELPA?

Eric


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Add-explicit-instructions-for-new-external-packages.patch --]
[-- Type: text/x-diff, Size: 1098 bytes --]

From b33289dab83b5f5abe93e4385d322fbfe36a1b27 Mon Sep 17 00:00:00 2001
From: Eric Abrahamsen <eric@ericabrahamsen.net>
Date: Mon, 14 Aug 2017 08:56:11 -0700
Subject: [PATCH] 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 322392997..48c105994 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:
 
-- 
2.14.1