I'm sorry to say, but Automatic, delta updates is a different language to me. I don't know what you mean by it. If delta updates refers to something else other than https://github.com/FreeCAD/FreeCAD/releases for the windows development channel. I am completely lost.

I will setup the package to include Package Parameters that will allow the installing user to decide were to have FreeCAD to be installed.
Does the exe install have a directory option/switch?

Thanks for the assistance.
RB

Delta updates:

A delta update is an update that only requires the user to download the code that has changed, not the whole program. It can significantly save time and bandwidth. The name is drawn from the fact that the Greek letter delta, Δ or δ, is used to denote change in mathematical sciences.

A delta update is an update that only requires the user to download the code that has changed, not the whole program.

I appreciate all the help, but I do require a little more assistance. Since Kunda1 mentions the dev updates are to be delta updates.

The Chocolatey default location for extraction of zip files is a lib folder deep inside the system directory structure. I'm fairly sure no one wants to have to find this location or use it for FreeCAD.

I just would like to ask for a general directory location for these updates (ex: C:\FreeCAD_Delta )?

Also Would the FreeCAD Community want/need Desktop Shortcuts to the delta update executable files?

These are needed for me to proceed in developing this package further in Chocolatey
Thanks again for the Assistance
RB

I appreciate all the help, but I do require a little more assistance. Since Kunda1 mentions the dev updates are to be delta updates.

Sorry I missed this until now.

The binary packages for the dev builds on Windows, provided on the releases page, are not delta updates. This is a goal and I probably confused this when i asked earlier if Chocolatey had this capability. From dev build to dev build only a small portion of the files change, but the release page dev builds require a download of the full package. We have tried some experiments where I have uplaoded only the changed files and these were to be copy/replaced over an existing build, the required download was decreased by about 80%. This had the disadvantage that files that were renamed/deleted remained on the users's system. If Chocolatey does not have a "diff" capability you can ignore this.

So lets drop the discussion of delta updates and focus on what is remaining. @redbaron2 has some pending issues:
1. Where to install FreeCAD dev version on windows? (Where is FreeCAD dev version being installed in Windows in general?)
2. Should chocolatey automatically create a link to the desktop?

In regards to #2 I'm wondering if chocolatey can query the user about this? If not, then perhaps we just skip this step ?

So lets drop the discussion of delta updates and focus on what is remaining. @redbaron2 has some pending issues:

For 1. on Win the dev builds are not installed. I usually just use 7zips extract here. This makes a folder in downloads that has the same name as the full package name.
For 2. If the file is un-zipped (or installed) to something like "C:\Users\Chris\AppData\Local\FreeCAD-dev" then it would be disariable to create a desktop shortcut, maybe called FreeCAD-dev, so stable and dev exist side by side.