You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently use the bzip2 binary to compress release archive and the -j flag to tar to unpack bzip2 archives. This is problematic for portability and also inconvenient for platforms that don't ship with bzip2 (like Windows and increasingly Linux distributions since bzip2 is losing popularity to newer compression standards like XZ or Zstd that are used for packages these days).
As such we should replace our usage of bzip2. Alternatives could be camlbz2 (to keep the exact same compression format at the cost of staying with an increasingly exotic choice) or camlzip which supports gzip and sacrifice some compression ratio while using a popular library and a format that won't go away for decades.
The text was updated successfully, but these errors were encountered:
We currently use the
bzip2
binary to compress release archive and the-j
flag totar
to unpack bzip2 archives. This is problematic for portability and also inconvenient for platforms that don't ship withbzip2
(like Windows and increasingly Linux distributions since bzip2 is losing popularity to newer compression standards like XZ or Zstd that are used for packages these days).As such we should replace our usage of
bzip2
. Alternatives could becamlbz2
(to keep the exact same compression format at the cost of staying with an increasingly exotic choice) orcamlzip
which supportsgzip
and sacrifice some compression ratio while using a popular library and a format that won't go away for decades.The text was updated successfully, but these errors were encountered: