Add AppImage packaging for Yakut
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- github-actions, linux, python
- Domain
- build-system, ci-cd, cli
Research direction
Start by reviewing the Yakut CI configuration and the current Python/Yakut dependency packaging described in the issue. Define the supported Linux and glibc range, then verify that CI produces a downloadable AppImage that runs on the documented platforms.
Written by the indexing model from the issue text.
Description
Hello! I've been looking at ways of reducing the complexity of the install of Yakut and reducing the variance in the combination of Python/Yakut/dependencies for users within my organization. I've been playing with AppImage packaging and have been bundling a specific Python version, Yakut, deps, and our DSDL so that installing and being able to interact with our Cyphal nodes is as simple as grabbing the single file and running it in a terminal.
So far I've found that packaging Yukut on Ubuntu 20.04 for use on Ubuntu 20.04/22.04 is fairly simple. Packaging for use on a wider range of Linux platforms (e.g. those with older glibc etc than Ubuntu 20.04's) is trickier.
I think that including the build of an AppImage into the Yakut CI here, so that it can be downloaded from GitHub would be very useful for many consumers.
While such a build may not be able to take advantage of the deeper integration by including vendor-specific DSDL, or hardcoding the configuration of e.g. CAN interfaces, it would certainly reduce the surface area of versions of dependencies that a majority of users would experience and hopefully provide a useful "does the AppImage work for you?" response to troubleshooting questions.
Happy to discuss further and contribute my work so far.
- Dominant language
- Python
- Stars
- 69
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OpenCyphal/yakut
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
OpenCyphal/yakut#116 ·
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 70/100
OpenCyphal/yakut#107 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
OpenCyphal/yakut#118 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
OpenCyphal/yakut#115 ·
-
Improve UIOpen
Difficulty 4/5 3-5 days Newbie friendliness 25/100
OpenCyphal/yakut#114 · 1 comment ·
All issues in OpenCyphal/yakut
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
py-econometrics/pyfixest#2072 ·
Maintainers usually reply within 1 day
-
~planning docs
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Kromatic-Innovation/athenaeum#3084 ·
Maintainers usually reply within 1 day
-
Bosch Room Thermostat II number entities offer -500 to 3000 °C setpoint limits and a -32768 to 32767 °C outdoor temperaturePossibly taken @zigpy-review-bot claimed this today. Openbot: code audit
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
zigpy/zha-device-handlers#5769 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 80/100
R0Y00/Xbox2Windows#254 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kludex/python-multipart#375 ·
Maintainers usually reply within 1 day