From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-devel@gnu.org
Subject: Re: [ELPA] Package proposal: EBDB
Date: Mon, 14 Aug 2017 08:59:47 -0700 [thread overview]
Message-ID: <87mv722l8s.fsf@ericabrahamsen.net> (raw)
In-Reply-To: jwvfucumqs5.fsf-monnier+gmane.emacs.devel@gnu.org
[-- 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
next prev parent reply other threads:[~2017-08-14 15:59 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-30 19:18 [ELPA] Package proposal: EBDB Eric Abrahamsen
2017-07-31 0:49 ` Richard Stallman
2017-07-31 3:10 ` Eli Zaretskii
2017-07-31 3:12 ` Eric Abrahamsen
2017-07-31 3:28 ` Eli Zaretskii
2017-07-31 3:30 ` Eric Abrahamsen
2017-08-09 21:17 ` Eric Abrahamsen
2017-08-13 1:03 ` Eric Abrahamsen
2017-08-13 21:47 ` Stefan Monnier
2017-08-14 1:44 ` Eric Abrahamsen
2017-08-14 9:45 ` Stefan Monnier
2017-08-14 15:59 ` Eric Abrahamsen [this message]
2017-08-14 23:15 ` Stefan Monnier
2017-08-14 23:50 ` Eric Abrahamsen
2017-08-15 7:49 ` Stefan Monnier
2017-08-15 15:30 ` Eric Abrahamsen
2017-08-17 16:57 ` Eric Abrahamsen
2017-08-17 22:21 ` Stefan Monnier
2017-08-17 22:52 ` Eric Abrahamsen
2017-08-17 23:27 ` Stefan Monnier
2017-08-17 23:31 ` Eric Abrahamsen
2017-08-01 5:33 ` John Wiegley
2017-08-01 16:04 ` Eric Abrahamsen
2017-08-01 22:25 ` John Wiegley
2017-08-01 23:52 ` Eric Abrahamsen
2017-08-02 1:28 ` John Wiegley
2017-08-02 3:08 ` Eric Abrahamsen
2017-08-01 5:58 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2017-08-06 22:12 Roland Winkler
2017-08-07 0:44 ` Eric Abrahamsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mv722l8s.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.