-
Notifications
You must be signed in to change notification settings - Fork 132
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
Distribution-agnostic packaging (Flatpak, AppImage, Snap) #685
Comments
FYI, a fix has been merged for the Zeek issue zeek/zeek#928 that was blocking progress on this one. |
A community user also pointed out:
Indeed, it seems appropriate for us to widen the scope of this issue to be about any/all of these approaches rather than specifically just Flatpak. |
On the AppImage front, @mason-fish recently pointed out:
|
A community user on Slack recently voiced a recommendation for the AppImage approach. An excerpt:
I'll mark this issue as an MVP1 target and perhaps try to take it up myself in that timeframe. Of course, if anyone from the community is watching this issue and manages to get it working before then, feel free to chime in with what you've got and I can work to incorporate it into our release process. |
A couple of users have expressed interest in a flatpak release of brim (see https://flatpak.org/). I had made some progress on this but ran into an issue with getting zeek to run. Flatpak uses OSTree which deduplicates redundant files by hard linking them from a single source. This caused an issue with zeek, which crashed while loading the baseline zeek scripts. zeek/zeek#928 has been filed to fix this.
We've discussed internally some ways we could hack around this. The plan right is to wait for the fix to land in zeek before moving forward on this.
The text was updated successfully, but these errors were encountered: