triplus wrote: ↑Mon Apr 08, 2019 9:43 pm
OK, today i started tackling the recipe for creating an AppImage based on Ubuntu 16.04 and by using FreeCAD 0.18 package from the stable PPA.
I have a local backup of "FreeCAD_0.18.16093.glibc2.17-x86_64.AppImage" I don't know why it's trimmed from the github/releases.
It would be great if I could unpack it, add the docs, and repack (It's based on 14.04) for 0.18.0
Going forward we will need to use 16.04, and unfortunately this will be PY2/QT4 unless we make a bunch of 16.04 packages for the PPA. For 0.18.1 maybe we can just pack/add docs/unpack this.
triplus wrote: ↑Mon Apr 08, 2019 9:43 pm
What is the plan for Conda, regarding documentation? A package to be created or adding/using the documentation from the releases page is excepted?
Both would be acceptable IMHO, or even without the docs. Right now this is our best path to PY3/QT, for the AppImages. I think this is top priority. On newer Debian/Ubuntu this is being addressed. But for a distro agnostic bundle this is our best bet.
triplus wrote: ↑Mon Apr 08, 2019 9:43 pm
Is @bblacey the only one that has access to AppImage oriented Travis instance? @sgrogan?
I have commit access to the AppImage repo, but I think there are also some OAUTH keys that I don't have access to. I think changing this
https://github.com/FreeCAD/FreeCAD-AppI ... vis.yml#L3 should work but I'm not sure how
- DEPLOY_REPO=${DEPLOY_REPO:-FreeCAD/FreeCAD}is set? Maybe in @bblacey's scripts?
triplus wrote: ↑Mon Apr 08, 2019 9:43 pm
On Windows side i guess @sgrogan has already sorted it out. When it comes to FreeCAD 0.18 binaries provided from the releases page.
Almost,
https://forum.freecadweb.org/viewtopic. ... 90#p299746
For OSX I don't know how to proceed. You and @looo are leading the charge.