From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ivan Shmakov Newsgroups: gmane.emacs.devel Subject: Re: a few questions on GNU ELPA Date: Fri, 30 Jan 2015 20:24:39 +0000 Message-ID: <87iofohv94.fsf@violet.siamics.net> References: <87oatpkof7.fsf@passepartout.tim-landscheidt.de> <87r3ye3mf7.fsf@violet.siamics.net> <87zjd1zj0q.fsf@violet.siamics.net> <87k342zabt.fsf@violet.siamics.net> <874muvpz2m.fsf__26477.4647228935$1414013842$gmane$org@violet.siamics.net> <87siide1r2.fsf@violet.siamics.net> <87k3186mri.fsf_-_@violet.siamics.net> <871tmlpngt.fsf@violet.siamics.net> <87r3udk8e6.fsf_-_@violet.siamics.net> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1422649532 14260 80.91.229.3 (30 Jan 2015 20:25:32 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 30 Jan 2015 20:25:32 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 30 21:25:25 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1YHI84-0007d1-J9 for ged-emacs-devel@m.gmane.org; Fri, 30 Jan 2015 21:25:24 +0100 Original-Received: from localhost ([::1]:38536 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YHI83-0007j5-Kr for ged-emacs-devel@m.gmane.org; Fri, 30 Jan 2015 15:25:23 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43968) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YHI7l-0007ey-Rv for emacs-devel@gnu.org; Fri, 30 Jan 2015 15:25:10 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YHI7j-00027w-Pt for emacs-devel@gnu.org; Fri, 30 Jan 2015 15:25:05 -0500 Original-Received: from fely.am-1.org ([2a01:4f8:d15:1b86::2]:36938) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YHI7j-0001xA-9K for emacs-devel@gnu.org; Fri, 30 Jan 2015 15:25:03 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=siamics.net; s=a2013295; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID:In-Reply-To:Date:Sender:References:Subject:To:From; bh=nnqsOqLJuZXdwiXw2sbFvJAwdGoicJbDWBzsSbaYCPY=; b=q3zsjG7D3PnL463Ja6tu2EPOc/dQcfyT1mmVjAzQQlcBH++g836hvTij81+KJV1WEuOi/4gFg6hmTlEKvm7JuXZxc9Q+JDbEoZCQ8DuTsPnH2xWhpM9t7wHpNG+d+xzW8KQ5I/W/YB+kseoSEVA+2Kf696kOed0CMGwxvajxVqc=; Original-Received: from [2a02:2560:6d4:26ca::1:1d] (helo=violet.siamics.net) by fely.am-1.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1YHI7U-0003Iq-4Z for emacs-devel@gnu.org; Fri, 30 Jan 2015 20:24:48 +0000 Original-Received: from localhost ([::1] helo=violet.siamics.net) by violet.siamics.net with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1YHI7M-0002ZN-78 for emacs-devel@gnu.org; Sat, 31 Jan 2015 03:24:40 +0700 Mail-Followup-To: emacs-devel@gnu.org In-Reply-To: (Stefan Monnier's message of "Thu, 29 Jan 2015 11:06:11 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a01:4f8:d15:1b86::2 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:182090 Archived-At: >>>>> Stefan Monnier writes: >> Reading elpa/README left me with a few unanswered questions. First >> of all, =E2=80=93 when the package is of the multi-file variety, would = the >> =E2=80=9Crelease machinery=E2=80=9D be somehow offended should I import= the >> pre-release history /without/ the respective PKG/PKG.el file, =E2=80=93= used >> (AIUI) for its Version: metadata field? (I=E2=80=99ll then push that f= ile >> in a separate =E2=80=9Crelease=E2=80=9D commit.) > If the .el file is missing from the HEAD revision, the nightly > deployment scripts may complain (to me), but if it's just missing in > some previous revision, that's of no consequence. ACK, thanks. >> Now, that same file is going to have a dozen lines of code >> (excluding comments) at most (that is: mainly the =E2=80=98defgroup=E2= =80=99 and >> =E2=80=98provide=E2=80=99 forms.) Should I use the GPL3+ notice for th= at file (as >> the rest of the code uses), or would the simple all-permissive >> license [1] be also acceptable? > For auctex.el I just used the standard GPL3 notice. Saved me some > valuable thinking ;-) I believe that claiming GPLv3+ over a file which is probably not copyrightable in the first place is somewhat misleading. Furthermore, given that Emacs itself has files bearing that same notice (see leim/MISC-DIC/cangjie-table.cns, for instance, and also a few more also under leim/), I guess it will do no harm to have a trivial .el so licensed in GNU ELPA. Or will it? >> Also regarding the release machinery, do I understand it correctly >> that there=E2=80=99s currently no way to maintain several (say, >> =E2=80=9Cdevelopment=E2=80=9D and =E2=80=9Cstable=E2=80=9D) branches in= GNU ELPA? > That's right. Of course, you can keep a "development" branch > somewhere in elpa.git if you want, but the GNU ELPA deployment > scripts won't know anything about it. ACK, thanks. BTW, as the resulting .tar file is going to differ to the one I=E2=80=99ve previously made available, does it make sense to use something like 0.1.1 for the GNU ELPA version, so to avoid the availability of two /different/ mw-0.1.tar files? (I=E2=80=99d rather use something like 0.1-elpa instead, but that isn=E2=80=99t going to be accepted by version-to-list.) --=20 FSF associate member #7257 http://boycottsystemd.org/ =E2=80=A6 3013 B6A0= 230E 334A