Select and Monitor Installation Path For Portables

[zero77]

When initially installing portable applications can you add an option for a default path, that will then be used when updating the application.
Thanks

[ferventcoder]

You mean like in the package directory or outside? We have a ChocolateyToolsFolder, however there are benefits to keeping a portable in the packaging folder that are not realized when it is put outside of there.

[ferventcoder]

Here is the considerations in much more detail - https://github.com/chocolatey/choco/issues/1303#issuecomment-303804561

[zero77]

so something like this ?

choco install sysinternals Install-ChocolateyPath -PathToInstall "C:\Users\User\Desktop\TEST"

[ferventcoder]

The comment I pointed you to was from the perspective of the creation of the package.

[ferventcoder]

We are looking at adding an installation directory override in the licensed edition to match what we do for installers. That might match closer with what you are looking to do?

[zero77]

Ok, I see so it’s not currently supported.
Yes, a directory over right is what I am looking for.
Thanks

[joyliao]

2017年7月14日 下午5:44，"zero77" <[email protected]>寫道： Ok, I see so it’s not currently supported. Yes, a directory over right is what I am looking for. Thanks — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1360 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJl4gOdffxYJ50iK-pkFU88nYOp_y6cjks5sNziCgaJpZM4OXOaF> .

[stevenwdv]

Is it currently possible to set the installation path for portable tools? I like to have them all in C:\prog but setting $env:ChocolateyToolsLocation does not seem to do anything as it still installs to C:\ProgramData\chocolatey\lib.

[TheCakeIsNaOH]

@stevenwdv Yes, it is, possible.

However, the package itself will still always install to $env:ChocolateyInstall\lib\<package name>.

So you need to add a chocolateyinstall.ps1 and manually copy over the required files to $env:ChocolateyToolsLocation, or unzip to there if the software comes in an archive.

[stevenwdv]

@TheCakeIsNaOH Ok but is it also possible with an existing chocolateyinstall.ps1 of a portable utility? E.g. https://community.chocolatey.org/packages/cports does not seem to do this, does it?

[TheCakeIsNaOH]

Correct, it does not have that ability. You would have to ask the maintainer to allow selection of the install location, or wait for this feature to be implemented in the licensed editions as mentioned above and then purchase a license.
chocolatey/chocolatey-licensed-issues#7

[stevenwdv]

@TheCakeIsNaOH That's a pity... I guess I could use symlinks and stuff instead.. Any particular reason why this will only be in the licensed version? It seems like a pretty easy function to implement.
By the way, am I misunderstanding what this current issue is for or is it the same feature?

[TheCakeIsNaOH]

Any particular reason why this will only be in the licensed version? It seems like a pretty easy function to implement.

🤷, perhaps because the licensed version already has an override for installers.

@ferventcoder would be the one answer that.

By the way, am I misunderstanding what this current issue is for or is it the same feature?

I think this issue is for a very similar feature. So it will definitely go into the licensed edition at some point, and it might go into open source as well at some point, but that is undecided as this still has the triaging tag.

[ferventcoder]

It seems like a pretty easy function to implement.

While some part of this could be easy to implement, there are a whole list of things that Chocolatey does (shimming, calls to items expected to be in a particular folder, etc) that does not make this as easy as most folks might think.

After much review and thought, this feels like the same feature that was tagged for licensed editions (Pro+).

[ferventcoder]

Duplicate of chocolatey/chocolatey-licensed-issues#7