Change how SoS Creates the Archive about sos HOT 3 CLOSED

We should also pick the compression based in part on the application being reported on. For example, I suspect most EAP users would want a .zip archive, even if generated on a RHEL box. They would expect a platform independent compression format to for reporting on a platform independent application. And, I would say nearly all java developers are very comfortable and have implementations of zip on whatever boxes they are working on. This is likely not true for other compression formats.

from sos.

One thing to consider is that when using PKZIP compression it would be aggravating to spool to a tar file first. If you are a user that wants to open a zipped sosreport and found a tarball inside you would then need to search for a tool to untar with.

from sos.

I think that the primary concern here should be to use the best available compression technology on the given platform and not whether or not a user has the proper tooling to unpack the resulting archive.

Most current benchmarks indicate that XZ is the reigning compression champion, as such, we should endeavour to use that where possible. On MS Win it isn't possible without some native libraries that aren't typically installed; therefore, on that platform we should use ZIP. On linux, XZ is readily available and we should always use it.

from sos.