2:43 p.m.
On 3/9/06, Robert Pluim <rpluim(a)gmail.com> wrote:
OK, what the heck is an EMACSPACKAGEPATH key doing in my registry?
And why
does (getenv "EMACSPACKAGEPATH") return its value. <sigh> I knew
running
windows was going to be painful again.
Robert -
Great detective work!
You really should remove that registry setting. It was probably set
by the 21.4.13 setup kit.
- Vin
--
Whoever you are, no matter how lonely,
the world offers itself to your imagination,
calls to you like the wild geese, harsh and exciting--
over and over announcing your place
in the family of things. Mary Oliver
3:16 p.m.
New subject: [Patch21.5] Find a relative package root at runtime
On 3/9/06, Vin Shelton <acs(a)xemacs.org> wrote:
You really should remove that registry setting. It was probably set
by the 21.4.13 setup kit.
I'm considering 'format c:; insert linux install cd' for that, but this is
my main work machine. ;-)
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...
Robert
3:45 p.m.
New subject: [Patch21.5] Find a relative package root at runtime
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
~\.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?
Robert
10 a.m.
New subject: [Patch21.5] Find a relative package root at runtime
"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/
1:04 p.m.
New subject: [Patch21.5] Find a relative package root at runtime
On 3/19/06, Adrian Aichner <adrian(a)xemacs.org> wrote:
Previous installers may have set EMACSPACKAGEPATH.
IIRC, the 21.4.13 cygwin install sets 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.
Yes, I can erase the setting of EMACSPACKAGEPATH from the registry at
install time, but I'm not sure that's the right thing to do. Maybe I
can detect it and allow the user the choice of clobbering
EMACSPACKAGEPATH. I'll investigate that option.
Volker - does the current cygwin kit set EMACSPACKAGEPATH?
Regards,
Vin
9:19 p.m.
New subject: [Patch21.5] Find a relative package root at runtime
"Vin Shelton" <acs(a)alumni.princeton.edu> writes:
On 3/19/06, Adrian Aichner <adrian(a)xemacs.org> wrote:
>
> Previous installers may have set EMACSPACKAGEPATH.
IIRC, the 21.4.13 cygwin install sets 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.
Yes, I can erase the setting of EMACSPACKAGEPATH from the registry at
install time, but I'm not sure that's the right thing to do. Maybe I
can detect it and allow the user the choice of clobbering
EMACSPACKAGEPATH. I'll investigate that option.
The latest setup kits I just uploaded now detect if EMACSPACKAGEPATH
is set and allow the person installing the chance to remove
EMACSPACKAGEPATH from the registry.
Regards,
Vin
12:22 a.m.
New subject: [Patch21.5] Find a relative package root at runtime
Vin Shelton <acs(a)xemacs.org> writes:
"Vin Shelton" <acs(a)alumni.princeton.edu> writes:
> On 3/19/06, Adrian Aichner <adrian(a)xemacs.org> wrote:
>>
>> Previous installers may have set EMACSPACKAGEPATH.
>
> IIRC, the 21.4.13 cygwin install sets 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.
>
> Yes, I can erase the setting of EMACSPACKAGEPATH from the registry at
> install time, but I'm not sure that's the right thing to do. Maybe I
> can detect it and allow the user the choice of clobbering
> EMACSPACKAGEPATH. I'll investigate that option.
>
The latest setup kits I just uploaded now detect if EMACSPACKAGEPATH
is set and allow the person installing the chance to remove
EMACSPACKAGEPATH from the registry.
Thank you, Vin, for implementing this feature!
Please let me know when the XEmacs website should be updated to
provide links to the latest stable and beta InnoSetup kits.
Vin, I would like to lay the updating of the relevant information in
your hands, after I have addressed any issues you may have.
Documentation would probably be the first one.
What would you like there?
Volker, it would be good to hear from you about this EMACSPACKAGEPATH
issue.
You also have still not answered our query about how we should
link to the cygwin installer from
http://www.xemacs.org/Download/win32/
Would be great to hear from you, Volker.
Best regards,
Adrian
Regards,
Vin
--
Adrian Aichner
mailto:adrian＠xemacs.org
http://www.xemacs.org/
6602
days inactive
6616
days old
6 comments
4 participants
participants (4)
-
Adrian Aichner -
Robert Pluim -
Vin Shelton -
Vin Shelton