Hi David,

Well it would be a temporary solution for two reasons.
1. New emacs releases would come with the new org-files.
2. All third-party code might by time move to the new files.
Thus, I thought this is a (maybe on a long perspective) temporary solution.

Other non-unix like OSes:
In that case, a small wrapper file, which replaces the old files might be the best solution, since it would work under all OSes. This wrapper could call the right functions within the new file and issues a warning/error/log that the call is deprecated. Hence it gives third-party maintainers (or anyone who jumps in) enough time to change the code. 


On 3 March 2013 13:26, David Engster <deng@randomsample.de> wrote:
Torsten Wagner writes:
> I didn't follow this thread in detail. But shouldn't it be enough to symlink
> e.g. org-icalendar against ox-icalendar. As far as I understood emacs would
> prioritize those local symlinks over the system wide installation. This would
> be a temporary solution until a new emacs release.

Why temporary? What about people installing Org 8.x on older Emacsen?

> Actually, under Linux, this is a pretty common way to bend
> dependencies towards the newest version of a lib.  Not sure for
> windows users.

Won't work on MS-DOS, and on Windows it is highly problematic for
various reasons (they're called "junctions" there; you need
administrator privileges to create them, and the upcoming Emacs 24.3
will be the first version to even support them).

-David