Chocolatey - Windows Package Manager that FreeCAD can be installed from

[Kunda1]

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.

[redbaron2]

Delta updates:

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

[Kunda1]

@sgrogan

This is out of my depth since I’m not a packager
@sgrogan would you mind responding to @redbaron2?

@redbaron2 thank you for you persistence

[sgrogan]

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.

If I’m not clear please ask for clarification.

@redbaron2 thank you for you persistence

+1

[Kunda1]

@easyw-fc

@Jb33G430

I appreciate all the help, but I do require a little more assistance.

@HoWil

@redbaron2 thank you for you persistence

+1

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 ?

[sgrogan]

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.

[Kunda1]

Moved to Packaging subforum

Downstream update: FreeCAD dev version is ready for testing on Chocolatey
https://github.com/chocolatey-community/chocolatey-coreteampackages/issues/1146#issuecomment-533203013
https://github.com/chocolatey-community/chocolatey-coreteampackages/pull/1277

[redbaron2]

Happy New Year FreeCAD Users

I have been working on updating my PR for the Chocolatey FreeCAD Package. I have it narrowed down to install the Development or Stable Releases which is the Good news.

Now for the BAD News
I just can’t get the Development builds to run at all in my test computer(s). I was under the impression that the zip contained everything needed to run FreeCAD.

Portable Releases
I was working on adding in the Portable versions as well to the package. This presented an interesting bug that I hope Kunda1 can answer. The past four portable releases have all had the extraction folder be everything from FreeCAD, conda-0.18.4, to having No Folder. I’m just asking if there can be some uniformity of these folders like the Development Releases?

[sgrogan]

Now for the BAD News
I just can’t get the Development builds to run at all in my test computer(s). I was under the impression that the zip contained everything needed to run FreeCAD.

I recently upgraded my compiler to VS2019 and I had some packaging issues with vsredist. I think this should be fixed in 0.19.19127 and above. Feedback welcome.

Portable Releases
I was working on adding in the Portable versions as well to the package. This presented an interesting bug that I hope Kunda1 can answer. The past four portable releases have all had the extraction folder be everything from FreeCAD, conda-0.18.4, to having No Folder. I’m just asking if there can be some uniformity of these folders like the Development Releases?

I’ll look into this, I didn’t make any changes on purpose

[redbaron2]

I recently upgraded my compiler to VS2019 and I had some packaging issues with vsredist. I think this should be fixed in 0.19.19127 and above. Feedback welcome.

Yes this version seems to run. I will test it later to see if it works on AppVeyor

I’ll look into this, I didn’t make any changes on purpose

Thanks

[Kunda1]

FreeCAD 0.19.x now packaged and distributed through Chocolatey

Original ticket: https://github.com/chocolatey-community/chocolatey-coreteampackages/issues/1146
PR: https://github.com/chocolatey-community/chocolatey-coreteampackages/pull/1277
Chocolatey 0.19.x page: https://chocolatey.org/packages/freecad/0.19.0.20052-dev

[redbaron2]

The Latest build of the FreeCAD 0.19 dev stream failed to build a windows

Win-Conda_vc14.x-x86_64.7z

version?

This failure will make and has made the current chocolatey package FreeCAD 0.19.0.20052-dev not installable.

I’m curious to find out if this was a error or a build fault?
Thanks for any help with this issue.

kunda1, sgrogan do either of you know what might have happen?

[Kunda1]

kunda1, sgrogan do either of you know what might have happen?

No idea. Anybody able to chime in?

[sgrogan]

kunda1, sgrogan do either of you know what might have happen?

Travis timed out 7ziping the package.
Should be fixed?
https://travis-ci.org/github/FreeCAD/FreeCAD-AppImage/builds/700214140
https://github.com/FreeCAD/FreeCAD/releases/tag/0.19_pre

[redbaron2]

Thank You.
I was hoping it was something like a timing issue.

[Kunda1]

@redbaron2

@redbaron2 any idea what the issue here is ?

[Kunda1]

@sgrogan

pinged by pinger macro

@sgrogan we should add mention of chocolatey to the 0.19 release page.

Something to the effect of:

For windows users there the option of using [Chocolatey](> https://chocolatey.org/> ) to manage and track upstream 0.19 releases. The 0.19 package is available of it’s own [dedicated FreeCAD Chocolatey package page](> https://chocolatey.org/packages/freecad> )

[sgrogan]

Something to the effect of:

done

[Kunda1]

done

Thx!

[redbaron2]

@Kunda1

I will check to see what is the problem with the verification, but since it is a pre development build. I would not really worry about it.
The Chocolatey verification system doesn’t always test pre development builds.