You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To make sure that appimagetool can work with the produced binaries, we should build it and run a short smoke test (i.e., build an AppImage, e.g., of appimagetool itself). That way, we make sure we don't accidentally break the relation between the two projects.
The text was updated successfully, but these errors were encountered:
Won't that increase the build time in this repository tremendously? What is the advantage over just telling the appimagetool repository to trigger a build? (You referred to "dependency hell" but I don't quite understand how the solution proposed above is better.)
To make sure that appimagetool can work with the produced binaries, we should build it and run a short smoke test (i.e., build an AppImage, e.g., of appimagetool itself). That way, we make sure we don't accidentally break the relation between the two projects.
The text was updated successfully, but these errors were encountered: