From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Eric Abrahamsen Newsgroups: gmane.emacs.devel Subject: Re: Why are so many great packages not trying to get included in GNU Emacs? Date: Thu, 23 Apr 2020 14:57:23 -0700 Message-ID: <87d07xamrg.fsf@ericabrahamsen.net> References: <9mmFgzvrBwjt_n_VJyaJdXINraNi5HsGpwq-0MLeKiJA7kG2BQA4uywrzjyz7lpRS0OZDpjEi8lspOKYUA7P_QsODsDew_8nbH960G55fmY=@protonmail.com> <97DA7804-F647-4A1D-B8E0-AFFE7A324C64@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="39336"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Yuan Fu , Stefan Monnier , Emacs developers To: ndame Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Apr 23 23:58:24 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jRjrU-000A8u-L3 for ged-emacs-devel@m.gmane-mx.org; Thu, 23 Apr 2020 23:58:24 +0200 Original-Received: from localhost ([::1]:42790 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jRjrT-00047D-Na for ged-emacs-devel@m.gmane-mx.org; Thu, 23 Apr 2020 17:58:23 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:59858) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jRjqh-0003Sz-Gu for emacs-devel@gnu.org; Thu, 23 Apr 2020 17:57:47 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.90_1) (envelope-from ) id 1jRjqg-0003nd-MR for emacs-devel@gnu.org; Thu, 23 Apr 2020 17:57:35 -0400 Original-Received: from ericabrahamsen.net ([52.70.2.18]:34202 helo=mail.ericabrahamsen.net) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jRjqg-0003eK-66 for emacs-devel@gnu.org; Thu, 23 Apr 2020 17:57:34 -0400 Original-Received: from localhost (c-73-254-86-141.hsd1.wa.comcast.net [73.254.86.141]) (Authenticated sender: eric@ericabrahamsen.net) by mail.ericabrahamsen.net (Postfix) with ESMTPSA id 4B6CEFA098; Thu, 23 Apr 2020 21:57:25 +0000 (UTC) In-Reply-To: (ndame's message of "Thu, 23 Apr 2020 20:19:37 +0000") Received-SPF: pass client-ip=52.70.2.18; envelope-from=eric@ericabrahamsen.net; helo=mail.ericabrahamsen.net X-detected-operating-system: by eggs.gnu.org: First seen = 2020/04/23 17:57:26 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] X-Received-From: 52.70.2.18 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:247637 Archived-At: ndame writes: >> >> For this reason, while some GNU ELPA package maintainers can "just push" >> as they see fit, as it should be, others haven't yet been granted this >> right. This is a problem which we should solve, > > A simple solution which occurs to me that a script which has the necessary > permissions could pull the changes to its local repo and push from there > to ELPA. (This implies that the author pushes his changes to a public > place like GitHub, so the script can pull them from there.) > > The script pulls the changes from the external repo when a certain dedicated > file in the repo (e.g. ELPA.pull) changes. The author changes this file > when he wants to authorize a new pull (wants to do a release to ELPA). > > The script can discover the changed trigger file either by regularly checking > the external repos of the ELPA packages which follow this protocol, or if it's > too much work then the author can send a mail to a dedicated mail address > which triggers the pull of his repo (e.g. sends a mail to elpapull@gnu.org > with the subject . I think it could be even simpler than that: ELPA is built every 24 hours right now. If we just registered external repos with ELPA, part of the build process could be pulling from those repos automatically, once per day. Package authors already have a mechanism for manually triggering a release: incrementing the package version number. There's no harm in ELPA bringing in new commits from the externals, if the author is still in control of when a new version is released. Eric