From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Achim Gratz Newsgroups: gmane.emacs.devel Subject: Re: package and testing rant (was Re: package.el, auto-installation, and auto-removal) Date: Tue, 11 Nov 2014 19:20:54 +0100 Organization: Linux Private Site Message-ID: <878ujhtx89.fsf@Rainer.invalid> References: <87a943umku.fsf@lifelogs.com> <87ppcvm7fj.fsf@newcastle.ac.uk> <87vbmndk46.fsf@lifelogs.com> <87wq72ls2h.fsf@ferrier.me.uk> <87k332lnn3.fsf_-_@ferrier.me.uk> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1415730098 10691 80.91.229.3 (11 Nov 2014 18:21:38 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 11 Nov 2014 18:21:38 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Nov 11 19:21:32 2014 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 1XoG4I-0006Ux-En for ged-emacs-devel@m.gmane.org; Tue, 11 Nov 2014 19:21:30 +0100 Original-Received: from localhost ([::1]:50164 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XoG4I-00006V-2f for ged-emacs-devel@m.gmane.org; Tue, 11 Nov 2014 13:21:30 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:53877) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XoG40-00006B-6j for emacs-devel@gnu.org; Tue, 11 Nov 2014 13:21:17 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XoG3u-0003Iq-Ly for emacs-devel@gnu.org; Tue, 11 Nov 2014 13:21:12 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:52750) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XoG3u-0003Ii-FW for emacs-devel@gnu.org; Tue, 11 Nov 2014 13:21:06 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XoG3s-000646-KK for emacs-devel@gnu.org; Tue, 11 Nov 2014 19:21:04 +0100 Original-Received: from pd9eb1af4.dip0.t-ipconnect.de ([217.235.26.244]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 11 Nov 2014 19:21:04 +0100 Original-Received: from Stromeko by pd9eb1af4.dip0.t-ipconnect.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 11 Nov 2014 19:21:04 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 43 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: pd9eb1af4.dip0.t-ipconnect.de User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) Cancel-Lock: sha1:UB8ZZXxnAV8OMdTHy0Tck/zVnk4= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 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:176775 Archived-At: Stefan Monnier writes: > The "magic step" that turns a directory in elpa.git into a tarball is > fairly limited currently. It is basically limited to "create > -pkg.el then tar". Given the desire to limit the number of external > tools required (which is why we distribute *.tar and not *.tar.gz, for > example), I think that "tar+untar" is pretty close to the minimum way to > transfer a directory of files from the developer's machine to the user > who installs the package. Yes, but for more complex packages this is too limiting. What gets packaged is only ever accidentally exactly the same as the source for that package. So the first question to decide would be if elpa.git is a source archive or a package archive. > Note that there is a fair bit a pressure to *add* rather than remove > magic steps (the first candidate in the list is to build the *.info > files from the *.texi files). ...if it is meant to be a source archive, this is actually quite sensible. Why check build results into a source archive? On the other hand, if it's just a package archive, then the implicit requirement is that the sources live someplace else. To give you an idea of what can be involved in moving from source to package, this is how Org creates its package archives: http://orgmode.org/cgit.cgi/org-mode.git/plain/mk/server.mk In words, the package and version file, a separate autoload file that Org needs (in addition to the autoload file that later gets created on the users' machine) and the documentation all need to be created before packaging things up. These steps actually happen in different directories (lisp/ and doc/) that get stripped directly by tar rather than copying the files around. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for KORG EX-800 and Poly-800MkII V0.9: http://Synth.Stromeko.net/Downloads.html#KorgSDada