Splitting off from https://forum.freecadweb.org/viewtopic. ... 3&start=60
The state of affairs right now
1. A semi-official (?) snap exists: https://snapcraft.io/freecad
The snap has improved over time, but issues remain:
- Its development sees extensive periods of inactivity. People are wondering whether it's still maintained: https://forum.snapcraft.io/t/is-freecad ... ined/27409
- It has a number of technical issues like not using file portal dialogs or not being able to download addons if the host has an /etc/gitconfig. Getting those fixed (e.g. https://github.com/opencomputeproject/CADCloud/pull/25) suffers from the problem outlined above
- It's attached to the CADCloud project, so no separate repo exists for its development.
- It does not use a self-contained packaging process as recommended when using snapcraft. You cannot just download the snapcraft folder and build a snap package.
- It is not registered under a proper organization account like "FreeCAD".
2. An unofficial snap exists, created by me: https://snapcraft.io/freecad-ppd
It solves many (if not all) issues I (and others) had with the snap above. Things like installing python packages within the snap (e.g. py_slvs for Assembly3), proper file dialogs, building in CI (GitHub Actions) etc. are implemented there.
I believe this could serve as the basis of a more modern snap package.
3. FreeCAD as an organization does not control its packages in one of the biggest "app stores" in Linux land
This follows from (1).
What I propose
1. create a repository under https://github.com/FreeCAD, e.g. https://github.com/FreeCAD/freecad-snap
2. host the packaging recipe in this repo. This can be done by copying my recipe. I'd gladly shut down my package if an official package existed.
3. create an account on https://snapcraft.io/ with the name "FreeCAD"
4. register an official snap. Consider requesting a transfer of the obvious "freecad" name. Anyone needing a special build of FreeCAD can easily create their own freecad package with a suffix (like mine, freecad-ppd).
5. grant trusted collaborators access to the snap, so you have a bus factor >1 for controlling the package
Maintaining an official snap package in the FreeCAD organization
Re: Maintaining an official snap package in the FreeCAD organization
Evidently, there's not much interest in an official snap, but at least freecad-ppd has seen some growth since the first proper publishing took place around six weeks ago. It has steadily grown to 217 weekly active devices. Not too shabby. Most people use the stable revisions (based on 0.19.3 and the previous 0.19.2).
Re: Maintaining an official snap package in the FreeCAD organization
where is the graph legend?
Alone you go faster. Together we go farther
Please mark thread [Solved]
Want to contribute back to FC? Checkout:
'good first issues' | Open TODOs and FIXMEs | How to Help FreeCAD | How to report Bugs
Please mark thread [Solved]
Want to contribute back to FC? Checkout:
'good first issues' | Open TODOs and FIXMEs | How to Help FreeCAD | How to report Bugs
Re: Maintaining an official snap package in the FreeCAD organization
Unfortunately, the legend only appears on mouse hover.
Re: Maintaining an official snap package in the FreeCAD organization
Three weeks later, we've grown quite a bit: 271 unique devices (+25%).
Most people are on the stable channel, the US & Germany have the lion's share of users.
Most people are on the stable channel, the US & Germany have the lion's share of users.
Re: Maintaining an official snap package in the FreeCAD organization
A new snap has emerged, this time published by the main developer RealThunder: https://snapcraft.io/freecad-realthunder
It is based on the unofficial freecad-ppd snap.
You can try it as an alternative to the AppImages if you want to test all the exciting stuff in his fork.
It is based on the unofficial freecad-ppd snap.
You can try it as an alternative to the AppImages if you want to test all the exciting stuff in his fork.
Re: Maintaining an official snap package in the FreeCAD organization
Still growing, we're up to 394 unique weekly-active devices. We've also increased the bus factor a bit: @Kunda1 has gained collaborator status in the Snap Store and on GitHub.
Re: Maintaining an official snap package in the FreeCAD organization
thanks for providing snaps for this! while i prefer flatpaks, ill take anything over manually managing appimages. is it possible to package the edge channel as weekly builds like appimages have? if im not mistaken, currently edge is built daily?
Re: Maintaining an official snap package in the FreeCAD organization
Yes.
There aren't plans to do a weekly build for snaps. It's either stable or edge (nightly)
Ref: Snap
Alone you go faster. Together we go farther
Please mark thread [Solved]
Want to contribute back to FC? Checkout:
'good first issues' | Open TODOs and FIXMEs | How to Help FreeCAD | How to report Bugs
Please mark thread [Solved]
Want to contribute back to FC? Checkout:
'good first issues' | Open TODOs and FIXMEs | How to Help FreeCAD | How to report Bugs
Re: Maintaining an official snap package in the FreeCAD organization
There are four risk levels for snaps (per track): edge, beta, candidate, stable.
Stable builds, i.e. tagged versions, land in candidate and get promoted to stable after some superficial testing.
Edge gets the nightly builds.
There's beta left, which could carry weekly promotions from edge. Would that make sense to lower traffic?