docker-spk icon indicating copy to clipboard operation
docker-spk copied to clipboard

Option to output contents to directory, skipping compression

Open garrison opened this issue 4 years ago • 5 comments

It would be nice if one could choose a lower compression ratio for the xz compression to speed it up. In my case, I immediately spk unpack the resulting spk (in order to spk 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.

garrison avatar Sep 01 '21 20:09 garrison

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.

zenhack avatar Sep 01 '21 22:09 zenhack

I'm thinking a --directory flag to docker-spk build.

zenhack avatar Sep 01 '21 22:09 zenhack

Yes, that would make even more sense.

garrison avatar Sep 01 '21 22:09 garrison

I realized a few things this evening.

  1. If my goal is to output the contents to a directory, skipping compression, then I can do this using Docker alone, bypassing docker-spk.
  2. Part of what precipitated me realizing the prior point and working around it is that I first realized that docker-spk build requires my keyring since it generates an intermediate spk. I wanted to adjust my development instructions in my port's README so that they would work for anyone.

I am still grateful that docker-spk got me started, even if I am not using it at the moment.

garrison avatar Sep 27 '21 02:09 garrison

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 spk unpack for the /proc stuff.

I'm going to leave this open though; it would still I think be reasonable to add this as a flag.

zenhack avatar Sep 27 '21 02:09 zenhack