From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chong Yidong Newsgroups: gmane.emacs.devel Subject: Re: How does ELPA work? Date: Tue, 08 Mar 2011 12:09:01 -0500 Message-ID: <87pqq15yky.fsf@stupidchicken.com> References: <87d3m9pou4.fsf@lifelogs.com> <87sjv1i89t.fsf@gmx.de> <87aah7rjkx.fsf@stupidchicken.com> <87hbbfnho3.fsf@gmx.de> <87vczumpa7.fsf@stupidchicken.com> <87mxl5933t.fsf@gmx.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1299604169 9355 80.91.229.12 (8 Mar 2011 17:09:29 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 8 Mar 2011 17:09:29 +0000 (UTC) Cc: Ted Zlatanov , emacs-devel@gnu.org To: Michael Albinus Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Mar 08 18:09:23 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Px0PS-0002u4-J1 for ged-emacs-devel@m.gmane.org; Tue, 08 Mar 2011 18:09:23 +0100 Original-Received: from localhost ([127.0.0.1]:48013 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Px0PM-0000RN-95 for ged-emacs-devel@m.gmane.org; Tue, 08 Mar 2011 12:09:16 -0500 Original-Received: from [140.186.70.92] (port=50133 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Px0PF-0000Q6-5a for emacs-devel@gnu.org; Tue, 08 Mar 2011 12:09:10 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Px0PD-0007Kd-2n for emacs-devel@gnu.org; Tue, 08 Mar 2011 12:09:08 -0500 Original-Received: from vm-emlprdomr-05.its.yale.edu ([130.132.50.146]:34606) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Px0PC-0007KC-UX for emacs-devel@gnu.org; Tue, 08 Mar 2011 12:09:06 -0500 Original-Received: from furball (dhcp128036014136.central.yale.edu [128.36.14.136]) (authenticated bits=0) by vm-emlprdomr-05.its.yale.edu (8.14.4/8.14.4) with ESMTP id p28H92YL001485 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 8 Mar 2011 12:09:02 -0500 Original-Received: by furball (Postfix, from userid 1000) id E1C32160308; Tue, 8 Mar 2011 12:09:01 -0500 (EST) In-Reply-To: <87mxl5933t.fsf@gmx.de> (Michael Albinus's message of "Tue, 08 Mar 2011 14:03:02 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) X-Scanned-By: MIMEDefang 2.71 on 130.132.50.146 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 130.132.50.146 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:136890 Archived-At: Michael Albinus writes: >> Uploaded (and accessible in packages/debbugs-0.1/ in the elpa branch). > > Thanks. However, I haven't seen the files in the elpa branch of Emacs > 24. Reading the rewritten admin/notes/elpa, it looks like I shall add > them there. Right? They are there. Maybe your copy of the branch is not up to date? Maybe you tried to do `bzr update', but did not bind your branch (in which case you should have done `bzr pull' to pull in changes)? > First, package-upload-file fails if the tar file is remote. I've fixed > this in package.el and simple.el (I had to make shell-command-to-string > aware of remote default-directory). Thanks. > Afterwards, uploading works, but it does not extract my tar file. I do > not know whether it shall be extracted by default, so I have done it > manually. Likely this was the origin of my problem, because now I can > install the package from the local archive. package-upload-file does not extract the tar file, because it's used to deploy a package directly into a package archive, to be downloaded by users. The elpa bzr branch works a bit differently. There we keep the packages in extracted (source) form, because the elpa branch does not itself function as a package archive. Instead, we run a script to deploy the package archive from it.