From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: feature/integrated-elpa 4f6df43 15/23: README added Date: Thu, 20 Oct 2016 10:21:08 +0300 Message-ID: <83y41jtriz.fsf@gnu.org> References: <20160916203414.25203.87032@vcs.savannah.gnu.org> <87wph96cto.fsf@russet.org.uk> <831szh3iq4.fsf@gnu.org> <87mvi5spl9.fsf@Rainer.invalid> <83mvi51y3b.fsf@gnu.org> <87instslxu.fsf@russet.org.uk> <83inst1vut.fsf@gnu.org> <87eg3ekjz2.fsf@russet.org.uk> <83vawpx677.fsf@gnu.org> <87h989ixxd.fsf@russet.org.uk> <83mvi1ww6m.fsf@gnu.org> <87wph5fw0w.fsf@russet.org.uk> <838ttlwodt.fsf@gnu.org> <878ttl3342.fsf@Rainer.invalid> <8360opwjs2.fsf@gnu.org> <8760oosrn8.fsf@russet.org.uk> <83shrsvj3g.fsf@gnu.org> <87k2d4fk9m.fsf@russet.org.uk> <83h988uzpm.fsf@gnu.org> <87eg3ce2s1.fsf@russet.org.uk> <83eg3cusfb.fsf@gnu.org> <8760oo86kb.fsf@russet.org.uk> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1476948156 28206 195.159.176.226 (20 Oct 2016 07:22:36 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 20 Oct 2016 07:22:36 +0000 (UTC) Cc: Stromeko@nexgo.de, emacs-devel@gnu.org To: phillip.lord@russet.org.uk (Phillip Lord) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Oct 20 09:22:32 2016 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 1bx7gG-0005rs-4g for ged-emacs-devel@m.gmane.org; Thu, 20 Oct 2016 09:22:24 +0200 Original-Received: from localhost ([::1]:52887 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bx7gI-0000jT-Bi for ged-emacs-devel@m.gmane.org; Thu, 20 Oct 2016 03:22:26 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44407) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bx7fL-0000i9-8I for emacs-devel@gnu.org; Thu, 20 Oct 2016 03:21:28 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bx7fH-0006Xw-9h for emacs-devel@gnu.org; Thu, 20 Oct 2016 03:21:27 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:39673) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bx7fH-0006Xs-6Q; Thu, 20 Oct 2016 03:21:23 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:4682 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1bx7fG-0003Qs-BF; Thu, 20 Oct 2016 03:21:22 -0400 In-reply-to: <8760oo86kb.fsf@russet.org.uk> (phillip.lord@russet.org.uk) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e 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:208527 Archived-At: > From: phillip.lord@russet.org.uk (Phillip Lord) > Cc: Stromeko@nexgo.de, emacs-devel@gnu.org > Date: Wed, 19 Oct 2016 20:47:16 +0100 > > Eli Zaretskii writes: > >> If everybody does the right thing. If not everybody does the right > >> thing, the old version gets loaded. Happened to me, it's hard to debug > >> and hard to work out what is going wrong. > > > > OK, so we agree that if everybody does the right thing, this will > > work. That's all we need at this point, because we certainly don't > > need to cater to packages which do the wrong thing: such packages will > > be fixed in no time, because they are bundled and are part of any > > Emacs installation. > > We should cater to packages which do the wrong thing, by ensuring that > the break quickly and obviously. No, we most definitely don't! We are talking about packages that are conceptually part of the Emacs core, even if they are maintained in another repository. Those packages will get all the attention they should from the Emacs developers, so we can safely assume this kind of problems will never happen in them, except by mistake that is corrected soon enough after it happens, like any other inadvertent breakage in Emacs.