-
-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
type2-runtime
version/commit should be informed in stdout
#80
Comments
I'm not sure whether we include those data in the runtime in some portable way. Right now, we just don't have that information. Plus, continuous is a moving target anyway. We've always considered it stable, though. But if we come up with a nice way to transport the information, we can for sure display it in appimagetool. In the future, we want to make actual releases of all components, then we can also, e.g., target the latest stable release. |
After creating an AppImage, appimagetool could simply run @brunvonlope in the meantime, your build script could of course simply do the same thing. |
We should have an option to detect that information statically, i.e., without the need for a suitable runtime environment. An ARM runtime cannot be run on an AMD64 system, but the AppImage could be built normally. |
Good point. |
When using appimagetool we know its version seeing the output:
However, it don't give any clue about what "version" (commit sha) of the runtime will be used:
Right now, developers need to rely on date and time of the creation of the appimage to get an estimative of what version/commit of the runtime is being used, which is imprecise. So, having this info in stdout would be very useful for debugging.
The text was updated successfully, but these errors were encountered: