On 4282 September 1993, J. wrote:
> I think this requires some changes in the policy:
> Common .el files could be installed in /usr{,/local}/share/emacsen/site-lisp
> which is not a standard location in Emacsen's path.
> It would replace /usr/{,/local}/share/emacs/site-lisp in both Emacsen
> paths and the problem would vanish.As elaborated elsewhere in this thread, I think that such a change requires an appropriate message when upgrading XEmacs. > Any other idea? No, but please note that it's in some respect only a partial solution, as it doesn't fix the two problems of possible load-path shadows (but that's okay, IMHO, it's not really solvable) and of binary incompatibilites. I.e., if the user tries to byte-compile any files in $PREFIX/emacsen/* it's likely that he ends up with *elc that just work under one version of Emacs. The policy should thus contain a note that files under emacsen should not be byte-compiled. The only clean way around this is to move any byte-compiled file to a version-specific directory. Holger -- --- http://www.coling.uni-freiburg.de/~schauer/ --- "You see, dear one-bit person, just because you have this magical inference engine that is churning out all sorts of things that nobody argues, does not mean that you arrive at conclusions that apply in this universe." -- Erik Naggum <[EMAIL PROTECTED]> in comp.lang.lisp -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
