-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
Option to output contents to directory, skipping compression #16
Comments
Hm, it seems like for your use case it might just be better to provide a way to skip building the .spk entirely, and just output the contents to a directory. |
I'm thinking a |
Yes, that would make even more sense. |
I realized a few things this evening.
I am still grateful that docker-spk got me started, even if I am not using it at the moment. |
Glad you worked your way through it. Yeah, it probably isn't actually helpful in your case then. Hopefully I'll eventually get around to supporting searchPath, so it isn't necessary to I'm going to leave this open though; it would still I think be reasonable to add this as a flag. |
It would be nice if one could choose a lower compression ratio for the
xz
compression to speed it up. In my case, I immediatelyspk unpack
the resulting spk (in order tospk dev
, but also for the fake-proc trick), so there is no sense in waiting for it to achieve maximum compression -- it only serves to slow down the development/test cycle.The text was updated successfully, but these errors were encountered: