From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eric Abrahamsen Newsgroups: gmane.emacs.devel Subject: Re: [ELPA] Package proposal: EBDB Date: Mon, 14 Aug 2017 08:59:47 -0700 Message-ID: <87mv722l8s.fsf@ericabrahamsen.net> References: <87efsxspgv.fsf@ericabrahamsen.net> <87mv784f1h.fsf@ericabrahamsen.net> <87shgwgtyp.fsf@ericabrahamsen.net> <87shgux6s1.fsf@ericabrahamsen.net> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" X-Trace: blaine.gmane.org 1502726763 2693 195.159.176.226 (14 Aug 2017 16:06:03 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 14 Aug 2017 16:06:03 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Aug 14 18:05:54 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dhHsD-00004v-Rw for ged-emacs-devel@m.gmane.org; Mon, 14 Aug 2017 18:05:49 +0200 Original-Received: from localhost ([::1]:58487 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dhHsI-00040r-CP for ged-emacs-devel@m.gmane.org; Mon, 14 Aug 2017 12:05:54 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52164) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dhHmo-0008NA-7S for emacs-devel@gnu.org; Mon, 14 Aug 2017 12:00:15 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dhHmi-0007jZ-KE for emacs-devel@gnu.org; Mon, 14 Aug 2017 12:00:14 -0400 Original-Received: from [195.159.176.226] (port=59124 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dhHmi-0007he-DZ for emacs-devel@gnu.org; Mon, 14 Aug 2017 12:00:08 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1dhHmR-0007z9-W5 for emacs-devel@gnu.org; Mon, 14 Aug 2017 17:59:51 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 78 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:kX381b7VnaZQ0TI7nZ8s1/Z8QbU= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:217541 Archived-At: --=-=-= Content-Type: text/plain Stefan Monnier 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 @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 --=-=-= Content-Type: text/x-diff Content-Disposition: attachment; filename=0001-Add-explicit-instructions-for-new-external-packages.patch >From b33289dab83b5f5abe93e4385d322fbfe36a1b27 Mon Sep 17 00:00:00 2001 From: Eric Abrahamsen 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/' 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/. For example: + + git push elpa master:externals/ + +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 --=-=-=--