triplus wrote: ↑Thu Apr 12, 2018 10:32 pm
That is strange as the way i understand it my PR build hasn't finished yet. And if it would it still wouldn't deploy. For macOS it should only deploy when PR is merged.
Looking closer maybe because there were Travis fails.
https://github.com/FreeCAD/FreeCAD/commits/master Once a merged commit passed all tests it was deployed.
triplus wrote: ↑Thu Apr 12, 2018 10:32 pm
I have a feeling somebody from the macOS team does that manually.
I don't think so. The fact that the backport was deployed to 0.18_pre suggests that it happens auto-magically.
triplus wrote: ↑Thu Apr 12, 2018 10:32 pm
No. Dependency would likely need to be set explicitly. Are you interested in creating/providing such Appimage?
No, the exact opposite. The offline docs are huge and don't change. The windows developer builds don't include them for this reason. I added a "doc" package to the releases page. I think this is cross platform, I haven't tested if this can work from user .FreeCAD/doc or the like.
triplus wrote: ↑Thu Apr 12, 2018 10:32 pm
P.S. As we only have "backport releases" on the legacy/stable PPA. I am guessing the regular release AppImage would be hard to upgrade? Thinking about it further. Does it make sense to have release and "backport release" available on GitHub as "backport release" is the relevant one?
Thanks to NormandC this part is easy. The legacy PPA builds from FreeCAD git releases/FreeCAD-0-16 branch ( and is easily changed in the recipe), stable PPA builds against FreeCAD git releases/FreeCAD-0-17, and daily builds against master.
The only complication is managing version.h
My understanding is that the daily appimage is built as a cron job with the daily PPA. Maybe something similar could be implemented for the stable PPA, but with a webhook or something so that ist's not built as a cron job when it doesn't change?