Comment 25 for bug 187290

Revision history for this message
Ulferikson (ulferikson) wrote :

> the patch to (179683) Works For Me(tm) on Vista.
> Haven't had the opportunity to try on XP.

Do you really need the patch? It is too easy to oversee an AppPath or PATH pointing to a working python install. Make sure you cannot use extensions without the patch and then try again with.

> If App Paths indeed need to be in HKLM on xp, then my
> patch is broken. I tried googling, but the information
> about App Paths was really thin,

I would use microsoft as reference on windows questions:
http://www.google.com/search?q=site:microsoft.com+app+paths

http://msdn2.microsoft.com/en-us/library/ms997545.aspx
"The system supports "per application" paths. If you register a path, Windows sets the PATH environment variable to be the registered path when it starts your application. You set your application's path in the AppPaths subkey under the HKEY_LOCAL_MACHINE key."

> However, why do we even set PATH at runtime? Shouldn't
> that be handled by the installer and if so, then there
> are no permission issues?

Using an installer is probably the normal "recommended" way, but you still cannot set HKLM as regular user and if you build Inkscape from source you wouldn't use an installer at all.