From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Alain Schneble Newsgroups: gmane.emacs.devel Subject: Re: feature/integrated-elpa 4f6df43 15/23: README added Date: Wed, 19 Oct 2016 12:25:38 +0200 Message-ID: <86k2d4r5y5.fsf@realize.ch> 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> <86twc8r8gw.fsf@realize.ch> <83r37cvfo6.fsf@gnu.org> <86oa2gr7jb.fsf@realize.ch> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1476872803 13807 195.159.176.226 (19 Oct 2016 10:26:43 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 19 Oct 2016 10:26:43 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (windows-nt) Cc: Stromeko@nexgo.de, emacs-devel@gnu.org, phillip.lord@russet.org.uk To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Oct 19 12:26:39 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 1bwo4u-00027K-LW for ged-emacs-devel@m.gmane.org; Wed, 19 Oct 2016 12:26:32 +0200 Original-Received: from localhost ([::1]:46818 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bwo4w-0008SU-Of for ged-emacs-devel@m.gmane.org; Wed, 19 Oct 2016 06:26:34 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35229) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bwo4q-0008SE-IF for emacs-devel@gnu.org; Wed, 19 Oct 2016 06:26:29 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bwo4p-0007A5-Ix for emacs-devel@gnu.org; Wed, 19 Oct 2016 06:26:28 -0400 Original-Received: from clientmail.realize.ch ([46.140.89.53]:4455) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1bwo4l-000779-Cu; Wed, 19 Oct 2016 06:26:23 -0400 Original-Received: from rintintin.hq.realize.ch.lan.rit (Unknown [192.168.0.105]) by clientmail.realize.ch with ESMTP ; Wed, 19 Oct 2016 12:26:07 +0200 Original-Received: from myngb (192.168.250.224) by rintintin.hq.realize.ch.lan.rit (192.168.0.105) with Microsoft SMTP Server (TLS) id 15.0.516.32; Wed, 19 Oct 2016 12:26:06 +0200 In-Reply-To: <86oa2gr7jb.fsf@realize.ch> (Alain Schneble's message of "Wed, 19 Oct 2016 11:51:20 +0200") X-ClientProxiedBy: rintintin.hq.realize.ch.lan.rit (192.168.0.105) To rintintin.hq.realize.ch.lan.rit (192.168.0.105) X-detected-operating-system: by eggs.gnu.org: Windows NT kernel [generic] X-Received-From: 46.140.89.53 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:208470 Archived-At: Alain Schneble writes: > Eli Zaretskii writes: > >>> From: Alain Schneble >>> CC: Phillip Lord , , >>> >>> Date: Wed, 19 Oct 2016 11:31:11 +0200 >>> >>> I think that regenerating *-loaddefs as Eli pointed out will solve the >>> effective issue at hand. What's not covered though is that it might >>> still be possible to explicitly load/require an old file that is no >>> longer there in the new version - e.g. (load "org-html") using the >>> example given by Phillip. >> >> The new version of Org will never do that. So you are talking about >> other packages that were not yet updated to follow suit, is that >> right? If so, is such explicit loading allowed? If it's allowed, >> it's a separate problem of dependencies between packages, and should >> exist with any arrangement of directories, I think. > > Exactly, I see it the same way. I also think it's as a separate issue > (that after all could also be handled by each package separately if it > needs to solve it at all). To elaborate what I wrote in parenthesis in the last sentence above: In this situation, the new package could still (provide 'the-deleted-feature) or register a function to be called when loading such deprecated file using after-load-alist or somesuch. The former could make a (require 'the-deleted-feature) a "noop", the latter could raise an error, or whatever. And there are for sure other feasible approaches that could be implemented by a package if required. Alain