From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Adam Porter Newsgroups: gmane.emacs.devel Subject: Re: NonGNU ELPA: New package: taxy.el Date: Thu, 26 Aug 2021 19:47:03 -0500 Message-ID: <87tujb7lyw.fsf@alphapapa.net> References: <8735qw7ybl.fsf@alphapapa.net> <87y28n7r2l.fsf@alphapapa.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="36809"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Aug 27 02:48:31 2021 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 1mJQ2o-0009Jx-Q1 for ged-emacs-devel@m.gmane-mx.org; Fri, 27 Aug 2021 02:48:30 +0200 Original-Received: from localhost ([::1]:53150 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mJQ2m-0006zi-SU for ged-emacs-devel@m.gmane-mx.org; Thu, 26 Aug 2021 20:48:28 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57462) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mJQ1f-0006FM-7N for emacs-devel@gnu.org; Thu, 26 Aug 2021 20:47:19 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]:52320) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mJQ1d-00067h-GC for emacs-devel@gnu.org; Thu, 26 Aug 2021 20:47:18 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1mJQ1a-0007t8-I5 for emacs-devel@gnu.org; Fri, 27 Aug 2021 02:47:14 +0200 X-Injected-Via-Gmane: http://gmane.org/ Received-SPF: pass client-ip=116.202.254.214; envelope-from=ged-emacs-devel@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action 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:273105 Archived-At: Stefan Monnier writes: >>> Why not GNU ELPA? > [...] >> Anyway, if you want to convince me to use GNU ELPA instead, I'm willing >> to listen. :) > > The way I see NonGNU ELPA is for packages which we Emacs maintainers > would like to see included in Emacs because they're important for the > whole Emacs community, but for some reason we were not able to collect > the needed paperwork. At least, that was the motivation behind the > creation of the NonGNU ELPA archive. > > taxy.el fails this test on 2 counts: > 1- we already have the paperwork. > 2- while it may be a handy package and may yet develop into > a cornerstone of Emacs, there aren't hordes of users > or packages that depend on it currently. > > Admittedly, some of the packages that were added lately to NonGNU also > fail the "importance" test, so it's probably not as important a criteria > as I thought it is. Well, I guess I wouldn't mind having it in ELPA instead of non-GNU ELPA. However, I like the idea of having ELPA automatically pull changes from my repo periodically, rather than having to push to a branch in the ELPA repo. I thought that to be possible, having tried to follow recent conversations about ELPA here, but reading the ELPA.git/README now, IIUC, that workflow is not supported for ELPA, only for non-GNU ELPA. Is that right? Or have I wildly misunderstood? :) Also, I'm keeping a few extra source files in the repo at the moment: - Some example applications in "examples/*.el", which I'll refer to in the documentation. - A magit-section-using library in "taxy-magit-section.el", which may or may not be suitable for publishing as a separate package at some point. Should these be included in the package so, e.g. users could refer to them from the Info manual, or should they be excluded, since they won't typically be loaded? (I'll add them to ".elpaignore" if they should be excluded, so I won't have to update the package recipe in ELPA itself later.) Thanks for your help.