From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: phillip.lord@russet.org.uk (Phillip Lord) Newsgroups: gmane.emacs.devel Subject: In Support of ELPA Date: Tue, 11 Jul 2017 22:46:36 +0100 Message-ID: <87eftmejer.fsf@russet.org.uk> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1499809620 10188 195.159.176.226 (11 Jul 2017 21:47:00 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 11 Jul 2017 21:47:00 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jul 11 23:46:53 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 1dV2zY-00027U-SU for ged-emacs-devel@m.gmane.org; Tue, 11 Jul 2017 23:46:49 +0200 Original-Received: from localhost ([::1]:49053 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dV2ze-0007YG-E9 for ged-emacs-devel@m.gmane.org; Tue, 11 Jul 2017 17:46:54 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54752) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dV2zS-0007Wk-95 for emacs-devel@gnu.org; Tue, 11 Jul 2017 17:46:43 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dV2zP-0001My-6f for emacs-devel@gnu.org; Tue, 11 Jul 2017 17:46:42 -0400 Original-Received: from cloud103.planethippo.com ([78.129.138.110]:44274) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dV2zO-0001MH-SS for emacs-devel@gnu.org; Tue, 11 Jul 2017 17:46:39 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=russet.org.uk; s=default; h=Content-Type:MIME-Version:Message-ID:Date: Subject:To:From:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=QwlStsqcs9gP6eFMAzBmvFjaxgEQaLedj+/IVxxL2rk=; b=Z+n2Coo0GWlsgpuwb93nbGzcg7 5SUh30Btdq3VBZZoUiL1qswGink/GI3mQECCLSMka9X3MMFo306o0EFGaHigPBOGBmdGbJ+plByUX ItlHPNhOGDYMMFalRt4sroa15sAsKYpQkteUnW97XhbjzqhlpAb71umEheYOEVG+Wl/u82sZWvZfr f+Ny4V+ZO3vikaFwV7fOvRimLnr+dK+A9wqOMTgk7kbnPsQJ0ALDJawvid2PXXooAjotCv2vc00P2 DoUWJyF+s5rDF4T1NpP4ZYZXGhspETJQqQ8HIofiKnC6Vz/1N8ok58oDTAXRzEmjy/Z7JeBDQXP9k MBtSITQg==; Original-Received: from cpc8-benw10-2-0-cust100.16-2.cable.virginm.net ([92.233.204.101]:47958 helo=russet.org.uk) by cloud103.planethippo.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89) (envelope-from ) id 1dV2zM-0010zt-S4 for emacs-devel@gnu.org; Tue, 11 Jul 2017 21:46:36 +0000 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cloud103.planethippo.com X-AntiAbuse: Original Domain - gnu.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - russet.org.uk X-Get-Message-Sender-Via: cloud103.planethippo.com: authenticated_id: phillip.lord@russet.org.uk X-Authenticated-Sender: cloud103.planethippo.com: phillip.lord@russet.org.uk X-Source: X-Source-Args: X-Source-Dir: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 78.129.138.110 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:216507 Archived-At: Following on from the emails about magit, I am going to have a go at getting copyright assignments for it, so that it can be included in either ELPA or Emacs. I've already discussed the pain points with the copyright assignment, but an additional issue is how to get code into ELPA. With dash.el, I added the dash repo as an "external" branch into ELPA. I think, though, this is still a bit clunky. I think it would be nice to add support for MELPA recipes directly in ELPA. This was adding an MELPA package to ELPA would require simply copying the recipe from MELPA. Assuming we support only MELPAs git (and github maybe) recipes, this could be done by either creating a new external branch for ELPA, or updating an existing branch from downstream. This functionality fits directly on topic of the existing ELPA code. Anyone have thoughts? And would any one be interested on adding it, as I will struggle to do this as well as working on assignments. Phil