"Program Files (x86)"/"Program Files" conventions not respected.

[GoogleCodeExporter]

Npackd64 will install everything (including 32 bit applications) into 
"C:\Program Files", while that is otherwise conventionally used only for x86_64 
applications

org.7-zip.SevenZIP -> C:\Program Files\7-ZIP
org.7-zip.SevenZIP64 -> C:\Program Files\7-ZIP_64_bit

This isn't too bad, since it is only a convention, and the name "Program Files" 
doesn't actually specify the architecture. 

But with NpackdCL (which is a 32-bit program installed in "Program Files 
(x86)"), you get something slightly more disturbing 

PS C:\> & 'C:\Program Files (x86)\NpackdCL\npackdcl.exe' add -p SevenZIP -p 
SevenZIP64
....
The package 7-ZIP 9.20 was installed successfully in C:\Program Files 
(x86)\7-ZIP
The package 7-ZIP 64 bit 9.20 was installed successfully in C:\Program Files 
(x86)\7-ZIP_64_bit

By disturbing, I'm referring to the path:
"Program Files (x86)\7-ZIP_64_bit"

The easiest solution would probably be to just not use "Program Files" or 
"Program Files (x86)" at all and instead use something like "C:\Npackd" by 
default. This would also be nicer as it doesn't have a space in the path.

Original issue reported on code.google.com by kevmi...@gmail.com on 25 Apr 2014 at 3:13

[GoogleCodeExporter]

Original comment by tim.lebe...@gmail.com on 25 Apr 2014 at 7:03

• Changed state: Thinking

[GoogleCodeExporter]

I was not able to reproduce the behavior with NpackdCL. It should use the exact 
same setting for the installation directory even if it is a 32 bit application. 
Could you please try to reproduce it and describe here exactly how you did 
this? Are you sure the newest NpackdCL is in the PATH?

Original comment by tim.lebe...@gmail.com on 27 Apr 2014 at 5:37

[GoogleCodeExporter]

0) Start on a freshly installed virtual machine that has had no previous 
install of Npackd
1) Download and install the GUI Npackd64-1.18.7.msi to C:\Program Files\Npackd 
(the default)
2) Install NpacdCL form the GUI (in this case it goes to C:\Program 
Files\NpackdCL)
3) Open up powershell and run
PS C:\> & 'C:\Program Files\NpackdCL\npackdcl.exe' add -p SevenZIP64
[0%] - Detecting installed software
[98%] - Installing / Installing 7-ZIP 64 bit 9.20 / Running the installation 
script (this may take some time)
[100%] - Installing
The package 7-ZIP 64 bit 9.20 was installed successfully in C:\Program Files 
(x86)\7-ZIP_64_bit

Original comment by kevmi...@gmail.com on 28 Apr 2014 at 2:22

[GoogleCodeExporter]

I should clarify, that the VM is Windows 7 64bit. And by fresh, I mean the only 
thing installed is Virtualbox Guest additions and windows updates.

Original comment by kevmi...@gmail.com on 29 Apr 2014 at 2:03

[GoogleCodeExporter]

Original comment by tim.lebe...@gmail.com on 29 Apr 2014 at 8:22

• Changed state: Accepted
• Added labels: Milestone-1.19

[GoogleCodeExporter]

I do not plan to change Npackd so that 32 bit programs are installed in 
"Program Files (x86)" and 64 bit programs are installed in "Program Files". As 
far as I know there is no difference between the two folders. There is also no 
information available in a repository if a package is a 32 bit or 64 bit one.

What will change is the behavior of NpackdCL. It should always choose "Program 
Files" by default on 64 bit systems exactly as the GUI.

Original comment by tim.lebe...@gmail.com on 29 Apr 2014 at 8:37

[GoogleCodeExporter]

That sounds reasonable.

Original comment by kevmi...@gmail.com on 30 Apr 2014 at 11:35

[GoogleCodeExporter]

Npackd 1.19.13 alpha is available: 
- 
https://sourceforge.net/projects/npackd/files/com.googlecode.windows-package-man
ager.Npackd64/
- 
https://sourceforge.net/projects/npackd/files/com.googlecode.windows-package-man
ager.Npackd/
- 
https://sourceforge.net/projects/npackd/files/com.googlecode.windows-package-man
ager.NpackdCL/
or from the unstable repository

Original comment by tim.lebe...@gmail.com on 23 Aug 2014 at 10:06

• Changed state: FixedPleaseTest

[GoogleCodeExporter]

Npackd 1.19.13 is the next stable release: 
https://code.google.com/p/windows-package-manager/wiki/Downloads?tm=2

Original comment by tim.lebe...@gmail.com on 6 Oct 2014 at 5:11

• Changed state: Fixed