From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Achim Gratz Newsgroups: gmane.emacs.devel Subject: Re: Adding ELPA to Emacs core Date: Mon, 12 Mar 2018 20:16:42 +0100 Organization: Linux Private Site Message-ID: <87ina1ayud.fsf@Rainer.invalid> References: <87efks1642.fsf@russet.org.uk> <83lgezu57f.fsf@gnu.org> <87k1ujzmn3.fsf@russet.org.uk> <87tvtmqnh5.fsf@russet.org.uk> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1520882492 13133 195.159.176.226 (12 Mar 2018 19:21:32 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 12 Mar 2018 19:21:32 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Mar 12 20:21:28 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1evT0g-0003Dx-KM for ged-emacs-devel@m.gmane.org; Mon, 12 Mar 2018 20:21:26 +0100 Original-Received: from localhost ([::1]:34178 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1evT2j-0000eS-8C for ged-emacs-devel@m.gmane.org; Mon, 12 Mar 2018 15:23:33 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:56081) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1evSwL-0004ow-Bf for emacs-devel@gnu.org; Mon, 12 Mar 2018 15:16:58 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1evSwG-0003gc-DZ for emacs-devel@gnu.org; Mon, 12 Mar 2018 15:16:57 -0400 Original-Received: from [195.159.176.226] (port=44644 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1evSwG-0003fi-7w for emacs-devel@gnu.org; Mon, 12 Mar 2018 15:16:52 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1evSuB-0002ya-8Z for emacs-devel@gnu.org; Mon, 12 Mar 2018 20:14:43 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 23 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:Go/YfpOlppgzU+TFd8xvLzt6Mf0= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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" Xref: news.gmane.org gmane.emacs.devel:223654 Archived-At: Phillip Lord writes: > One thing that does worry me is that it means Emacs source as references > to ELPA git. If Emacs (or ELPA) ever needs to move VCS, it's going to > require some significant hackery. Well, if you replace those SHA you were previously talking about with tags, then the required hackery gets significantly reduced. And no, I don't think that EMACS needs to be able to reference any SHA directly since ELPA is well enough under control to be able to place tags where you need them, maybe even of the form emacs-x.y.z or similar so it becomes clear which of these are in use where. Naming the tags explicitly to indicate Emacs' use of them would certainly help any maintainer who would want to backport important patches to a branch that older Emacsen can use. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Samples for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra