From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stephen Leake Newsgroups: gmane.emacs.devel Subject: Re: package and testing rant (was Re: package.el, auto-installation, and auto-removal) Date: Wed, 12 Nov 2014 11:00:45 -0600 Message-ID: <857fz0l5fm.fsf@stephe-leake.org> References: <87a943umku.fsf@lifelogs.com> <87ppcvm7fj.fsf@newcastle.ac.uk> <87vbmndk46.fsf@lifelogs.com> <87wq72ls2h.fsf@ferrier.me.uk> <87k332lnn3.fsf_-_@ferrier.me.uk> <878ujhtx89.fsf@Rainer.invalid> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1415811732 1533 80.91.229.3 (12 Nov 2014 17:02:12 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 12 Nov 2014 17:02:12 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Nov 12 18:02:05 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 1XobIy-0005ir-Lb for ged-emacs-devel@m.gmane.org; Wed, 12 Nov 2014 18:02:04 +0100 Original-Received: from localhost ([::1]:55898 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XobIx-0002PY-Dl for ged-emacs-devel@m.gmane.org; Wed, 12 Nov 2014 12:02:03 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35298) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XobHr-0001Rd-7n for emacs-devel@gnu.org; Wed, 12 Nov 2014 12:01:01 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XobHl-00024y-AZ for emacs-devel@gnu.org; Wed, 12 Nov 2014 12:00:55 -0500 Original-Received: from dnvrco-outbound-snat.email.rr.com ([107.14.73.228]:40527 helo=dnvrco-oedge-vip.email.rr.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XobHl-00024p-4B for emacs-devel@gnu.org; Wed, 12 Nov 2014 12:00:49 -0500 Original-Received: from [70.94.38.149] ([70.94.38.149:52516] helo=TAKVER) by dnvrco-oedge03 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id A7/30-05523-F3293645; Wed, 12 Nov 2014 17:00:48 +0000 In-Reply-To: (Stefan Monnier's message of "Wed, 12 Nov 2014 11:13:25 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.94 (windows-nt) X-RR-Connecting-IP: 107.14.64.142:25 X-Authority-Analysis: v=2.1 cv=B/s30YdM c=1 sm=1 tr=0 a=AppmJ/7ZOOFWL/q6u6u93g==:117 a=AppmJ/7ZOOFWL/q6u6u93g==:17 a=ayC55rCoAAAA:8 a=fNEgcOh0sVsA:10 a=9i_RQKNPAAAA:8 a=Wx-76dwXXAONP3Aoyv0A:9 X-Cloudmark-Score: 0 X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 107.14.73.228 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:176825 Archived-At: Stefan Monnier writes: >> that package. So the first question to decide would be if elpa.git is a >> source archive or a package archive. > > I want it to be a source archive. > > >> 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) > > The org-pkg.el file is nowadays built by the GNU ELPA scripts (there's > even a special exception in this script specifically for Org, which is > the only package where this file is not auto-built yet). > > What is the "version" file? > > Can you give further details on this extra autoload file? > >> and the documentation all need to be created before packaging >> things up. > > Right, the doc-generation is a step that's clearly lacking in the > current GNU ELPA scripts. Is the intent to build the docs on the GNU ELPA server, and include them in the tarball? Or to build them on the user's machine? I'm guessing the former, to avoid burdening users with tools. That requires standardizing the tools that the Gnu ELPA server provides. What will we do when packages start including source code for Emacs dynamic modules (ie curl, ada-mode parser)? That introduces user-specific parameters like OS, machine architecture, compiler version, etc. I've suggested one solution; use the existing (non-Emacs) OS packaging systems for those binaries; that avoids the issue for GNU ELPA. -- -- Stephe