ignisf

@supercodepoet, apart from the stylistic issues @houndci found in the PR, is there another reason you believe it should not be merged?

Hello, What is the rationale of this change? Why deviate from the cipher string recommended by the authors and used throughout this guide (see section 3.2.3. Recommended cipher suites)?

> Do you suggest it for making binaries available on more platforms or for other reasons? The benefits would be the following: 1. One could download a source distribution that...

OK, I now have all the tools except `pngout` which does not seem to be open-source and `svgo`. I consider my issue resolved

Yes. (I've added this to the README, thanks for reminding me). That's not unlike Nokogiri's deps on `libxml2-dev` and `libxslt-dev`, however those can be easily added to the gem itself...

If there's will to distribute a source version of image_optim_pack, I'd probably find some time to assist if needed. @aried3r, keep in mind that I've chosen not to publish ~~ignisf/crunch~~...

Hey, so I'll use https://rubygems.org/gems/libv8/versions as an example. If you're unfamiliar, v8 is a large library with a nasty build system. Its build takes about 20 minutes if you're lucky...

As a side note, V8 needs additional arch detection (on top of the one of rubygems) which I expect won't be necessary in this case. Also, introducing a dependency on...

Basically the issues one would meet with compiling from source are as you mentioned, the dependencies on libpng-dev, libjpeg-dev, zlib and nasm. With the latest few commits in ~~crunch~~ image_compressor_pack...

Just FYI, ~~`crunch`'s~~ `image_compressor_pack`'s build should now have no external library dependencies and binary gems can be produced with the `rake binary` task.