Installation directory

[GoogleCodeExporter]

Npacked does (try) to override the install directory. Is there any way to 
disable this. I think programs have good reasons for installing in the x86 or 
x64 directory. Or somethings even in C:\. Overriding this cause problems in 
case of python for example. Also some applications ignore the location. Ending 
in file's in both x86 and x64 program files.

Anyone other insides?

Original issue reported on code.google.com by Pimmetje on 28 Oct 2014 at 9:47

[GoogleCodeExporter]

No, there is no way to disable this behavior. AFAIK there is no reason to 
install 32 bit applications in "Program Files (x86)" other than convention.

What is the problem with Python?

Original comment by tim.lebe...@gmail.com on 28 Oct 2014 at 5:36

[GoogleCodeExporter]

Python among others does not like spaces in it's path. Thats why it installs in 
c:\pythinXYZ. So when i install it using npacked it does not always work as 
expected. And i think there other applications that are quite hooked to there 
default location.

I agree with u on most cases it does not matter if u use x86 or x64. And i do 
not care. Only i think it was created because u can have a x86 and  x64 version 
of the  application. In my opinion it would be the best if npacked would 
respect this standard. So if it's possible i would like to have a install 
location of package default if that possible.

Original comment by Pimmetje on 28 Oct 2014 at 7:04

[GoogleCodeExporter]

Python installation directory can be changed during a manual installation to 
any path. It is also possible to install Python in "C:\Program Files". The 
installer allows this and does not even show a warning. I would say Python 
works perfectly from directories containing spaces. 

As far as I understand you have problems with other software running on top of 
Python and installed without Npackd.

Probably 99% of all Windows programs run without any problems from directories 
with spaces. 

For your particular case I would suggest to change the Npackd installation 
directory to something like "C:\Programs" and install everything there.

The main reason to not allow programs to use their default installation path is 
to have all software in one directory (e.g if you do not have enough space on 
C:) and being able to find a package programmatically (e.g. from the command 
line using "npackdcl.exe path").

Original comment by tim.lebe...@gmail.com on 28 Oct 2014 at 9:21

[GoogleCodeExporter]

What would be be the disadvantage of adding it as a option in the dropdown?

Could u please check the package launchy & launchy putty plugin? Launchy will 
install in the x64 dir will the plugin will be placed in the x86 dir. 

Original comment by Pimmetje on 28 Oct 2014 at 10:04

[GoogleCodeExporter]

1. If you mean the drop-down control with the installation path you can enter 
any path there. It is a text edit box.

2. not yet sure how to fix the Putty for Launchy package. It is one of those 
cases where Launchy does not respect the Npackd installation directory and it 
is not clear how to find it.

Original comment by tim.lebe...@gmail.com on 29 Oct 2014 at 9:56

[GoogleCodeExporter]

Original comment by tim.lebe...@gmail.com on 7 Jan 2015 at 10:16

• Changed state: FixedPleaseTest

[GoogleCodeExporter]

Original comment by tim.lebe...@gmail.com on 7 Jan 2015 at 10:17

• Changed state: WontFix