-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Add support for snapcraft compression top-level key #5881
Comments
That sounds like a nice idea. Happy to accept a PR for this addition! |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Yes, it is.
My lack of time to work on it.
Well, I guess it's not that hard to implement, but I didn't really look at it. |
Here is the PR to fix this issue #6201 |
I think the PR is almost complete. @mmaietta maybe you can have a quick look over the proposed changes sometime soon. It would be great to land this in the near future. |
This is done via #6201 |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
I guess it's only a matter of this being released on a stable release. |
This is related to #7013 |
Snap packages are known for having a very long first startup time. That's mainly because snaps are compressed squashfs images using XZ algorithm. Recently Canonical made it possible to use LZO algorithm instead of XZ, which significantly improves startup time.
I'd like to ask for electron-builder to support the snapcraft top-level key
compression
. From https://snapcraft.io/docs/snapcraft-top-level-metadata:More info:
This is related to bitwarden/clients#2609
The text was updated successfully, but these errors were encountered: