"Robert Pluim" <rpluim(a)gmail.com> writes:
On 3/9/06, Robert Pluim <rpluim(a)gmail.com> wrote:
Hmm, I'm still going to have a look at why the 21.5 packages.el doesn't
find the package directories from EMACSPACKAGEPATH. The contents *look*
the same as configure-package-path...
So this is the way I read it:
packages.el uses packages-find-package-hierarchies on the components of
EMACSPACKAGEPATH, which in my case has the value
Vin's changes eliminate setting EMACSPACKAGEPATH in xemacs.mak.
~\.xemacs;C:\Program Files\XEmacs\site-packages;C:\Program Files\XEmacs\
xemacs-packages
Unfortunately, what it's doing is looking for 'site-packages' or
'xemacs-packages' as subdirectories of the components of that variable, which
obviously isn't going to work.
I can delete the registry key easily enough, but what about those people who
will be installing 21.5 on windows with an installer? Will we remove the key
for them, or do we need to change the packages.el logic?
Previous installers may have set EMACSPACKAGEPATH.
It's hard for current installers to know whether removing the registry
key is what the user wants.
Vin, would it be possible for InnoSetup to detect this old registry
settings and query the user whether the entry should be removed?
I think even telling the user about the issue at install-time would be
valuable.
Best regards,
Adrian
Robert
--
Adrian Aichner
mailto:adrianï¼ xemacs.org
http://www.xemacs.org/