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 17:56:50 -0500 Message-ID: <87y28n7r2l.fsf@alphapapa.net> References: <8735qw7ybl.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="22649"; 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 00:57:55 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 1mJOJn-0005fz-2C for ged-emacs-devel@m.gmane-mx.org; Fri, 27 Aug 2021 00:57:55 +0200 Original-Received: from localhost ([::1]:42664 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mJOJk-0000hF-TY for ged-emacs-devel@m.gmane-mx.org; Thu, 26 Aug 2021 18:57:52 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37424) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mJOIy-0008RH-BE for emacs-devel@gnu.org; Thu, 26 Aug 2021 18:57:04 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]:42822) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mJOIv-0007wx-H5 for emacs-devel@gnu.org; Thu, 26 Aug 2021 18:57:03 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1mJOIs-0004ZB-5j for emacs-devel@gnu.org; Fri, 27 Aug 2021 00:56:58 +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:273098 Archived-At: Stefan Monnier writes: >> I'd like to submit taxy.el to NonGNU ELPA: > > Why not GNU ELPA? Well, I'm not strictly opposed to that, but I'm not sure if I want to require copyright assignment to accept contributions to it. Of course, I understand why Emacs itself does so, and I tend to agree with that, but for my own packages, I'm not sure if it would be worth it. For example, I maintain a variety of Emacs-related packages, and none of them require CA. So what if, several months from now, someone proposed a contribution to taxy.el, and I forgot to ask for CA (because none of my other packages do, and I'm not in the habit of even thinking about that), and then it turned out they were unable to sign it? Would I be in trouble, or would the package be? Anyway, if you want to convince me to use GNU ELPA instead, I'm willing to listen. :) >> Following the nongnu README.org file, I was unable to test the "make >> build/taxy" step, because apparently my version of git doesn't have the >> "--no-track" argument to the "git worktree" command (and upgrading git >> manually is more than I want to do at the moment ;). But I assume that >> it will work correctly, because everything seems to be in order. > > Sorry 'bout that dependency. I could try and lift it, but then again > I had to upgrade the `git` on `elpa.gnu.org` because some of the > commands used hit bugs that caused it crash and those uses are hard to > eliminate, so I'm not sure it's worth the effort. Of course, no problem. I'll get mine upgraded at some point. >> 1. I didn't see anything about "externals" in the nongnu readme. >> Forgive me, because this has probably been rehashed many times here, but >> do I need to specify that manually, or is that the default for the >> nongnu repo? I do intend to maintain the package in my own repo. > > That's the assumption when you have `:url "...."` in the spec, yes. Great, thanks. >> 2. I currently have the version header on "0.1-pre". Do I need to use >> a "non-pre" version number in order for the package to be built and >> published on (nongnu) ELPA? > > Yes. The "0.1-pre" version will still appear in the ..-devel archive > (where we always build the latest revision regardless of the version > number), but not in the main one. That sounds good to me, thanks. I'll probably tag a 0.1 soon enough.