pombreda / windows-package-manager

Automatically exported from code.google.com/p/windows-package-manager
0 stars 0 forks source link

NodeJS x64 #413

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
I just installed nodeJS from npacked. npm was not added to my path. Now i 
reinstalled the one from the site. Now i have npm added to my path variable. I 
used default installation settings when doing the monual installation. 

I still would recommend adding a option to leave the installation settings 
default. 

I hope u don't mind me posting another issue. (i am currently in the process of 
reinstalling my PC. So i am just trying the document the problems i have). 

Original issue reported on code.google.com by Pimmetje on 29 Oct 2014 at 10:40

GoogleCodeExporter commented 9 years ago
In my opinion it is a good thing that the package does not modify the PATH 
variable. See 
https://code.google.com/p/windows-package-manager/wiki/IdealPackage#PATH for 
more details. I plan to use Exe Proxy (http://npackd.appspot.com/p/exeproxy) in 
the future to create "links" to actual executables from one directory 
(C:\ProgramData\Npackd\Commands or similar).

Npackd does not modify anything but the installation path. 

Your feedback is really appreciated.

Original comment by tim.lebe...@gmail.com on 29 Oct 2014 at 10:03

GoogleCodeExporter commented 9 years ago

Original comment by tim.lebe...@gmail.com on 2 Jan 2015 at 6:11

GoogleCodeExporter commented 9 years ago

Original comment by tim.lebe...@gmail.com on 3 Jan 2015 at 12:11