Re: feature/integrated-elpa 4f6df43 15/23: README added

[Alain Schneble]

Alain Schneble <address@hidden> writes:

> Eli Zaretskii <address@hidden> writes:
>
>>> From: Alain Schneble <address@hidden>
>>> CC: Phillip Lord <address@hidden>, <address@hidden>,
>>>     <address@hidden>
>>> 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