From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: Re: elpa.gnu.org repository sync with Emacs Date: Tue, 16 Nov 2010 09:14:53 -0600 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <87oc9p711u.fsf@lifelogs.com> References: <87mxpabjj3.fsf@stupidchicken.com> <8762vyz5rl.fsf@stupidchicken.com> <8739r2z1w8.fsf@stupidchicken.com> <87y68t8jif.fsf_-_@lifelogs.com> <87r5eljosw.fsf@stupidchicken.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1289920528 10826 80.91.229.12 (16 Nov 2010 15:15:28 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 16 Nov 2010 15:15:28 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Nov 16 16:15:22 2010 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 1PINFg-0002h2-9Z for ged-emacs-devel@m.gmane.org; Tue, 16 Nov 2010 16:15:20 +0100 Original-Received: from localhost ([127.0.0.1]:37438 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PINFf-00015b-6g for ged-emacs-devel@m.gmane.org; Tue, 16 Nov 2010 10:15:19 -0500 Original-Received: from [140.186.70.92] (port=53123 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PINFZ-00015J-Rt for emacs-devel@gnu.org; Tue, 16 Nov 2010 10:15:14 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PINFV-0001NR-74 for emacs-devel@gnu.org; Tue, 16 Nov 2010 10:15:13 -0500 Original-Received: from lo.gmane.org ([80.91.229.12]:43337) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PINFU-0001N2-AJ for emacs-devel@gnu.org; Tue, 16 Nov 2010 10:15:09 -0500 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1PINFQ-0002Z0-SV for emacs-devel@gnu.org; Tue, 16 Nov 2010 16:15:04 +0100 Original-Received: from 38.98.147.130 ([38.98.147.130]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 16 Nov 2010 16:15:04 +0100 Original-Received: from tzz by 38.98.147.130 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 16 Nov 2010 16:15:04 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 56 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: 38.98.147.130 X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/24.0.50 (gnu/linux) Cancel-Lock: sha1:srozur9uzBfw0xaEdTI/WWNSHGM= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) 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:132722 Archived-At: On Tue, 16 Nov 2010 10:01:03 -0500 Chong Yidong wrote: CY> Ted Zlatanov writes: >> 1) add elpa/ directory to main Emacs repo (as a branch or >> subdirectory; my vote is for a subdirectory that's not bundled or >> compiled because it will get branched together with Emacs itself). >> Make it available to a dev checkout of Emacs as a file:/// URL (so it >> can be tested easily). CY> I think it makes more sense to add elpa/ as a branch. Then we can just CY> `bzr merge' from savannah into the bzr repository used for elpa.gnu.org, CY> in order to grab the changes made by Emacs devs. (I don't think you can CY> `bzr merge' a subdirectory, or can you?) We would merge the whole Emacs repository into a repo on elpa.gnu.org. But only the elpa/ subdirectory would get deployed out of that repo, the rest would be there just to make the merge simpler. I think that's the easiest way. As I said, I think a subdirectory will allow branching which in turn will freeze the elpa/* packages for a particular version of Emacs (instead of making special branches for that purpose). That alone is worth the price of admission. CY> First, we should make a change to the elpa.gnu.org repository: CY> currently, the .tar packages live in the repositories as tarballs. We CY> should instead leave them as untarred directories, and put the script on CY> elpa.gnu.org in charge of tarring them up after `bzr export'. That way, CY> changes made to the contents of packages can be viewed with bzr CY> diff. No problem. That would just be a "make elpa" command in each directory and at the top. I agree tarballs are a pain for tracking so this works best. CY> Still unresolved is the problem of which packages should be considered CY> "OK" to tweak, and which should not. I don't relish the idea of having CY> to do a big merge every time a package is released upstream. I think we CY> should have a clear policy that only packages that are developed CY> principally inside the package bzr repository, or whose maintainer is CY> explicitly in charge of merging, should be hacked on. How about a "third-party" package repository, disabled by default but easily enabled, which would host externally hosted packages? We would fetch truly external packages such as org-mode into it with scripts, disconnected from the Emacs repo and the elpa.gnu.org deployment. And it would not be versioned: whatever is fetched today is what you get. That separates things nicely between "internal" and "external" elpa.gnu.org packages, with "internal" packages coming from the Emacs repo, versioned, and hacked regularly; "external" packages independent, fetched regularly, and maintained outside of Emacs. Ted