* Package name    : libminiz
  Version         : 3.1.0
  Upstream Contact: https://github.com/richgel999/miniz/issues
* URL             : https://github.com/richgel999/miniz
* License         : MIT
  Programming Lang: C, C++
  Description     : Miniz is a lossless data compression library

Miniz is a lossless, high performance data compression library that
implements the zlib (RFC 1950) and Deflate (RFC 1951) compressed data
format specification standards. It supports the most commonly used
functions exported by the zlib library, but is a completely independent
implementation so zlib's licensing requirements do not apply. Miniz also
contains simple to use functions for writing .PNG format image files and
reading/writing/appending .ZIP format archives. Miniz's compression
speed has been tuned to be comparable to zlib's, and it also has a
specialized real-time compressor function designed to compare well
against fastlz/minilzo.


This package is a dependency to github.com/shader-slang/slang which I
intend to open an ITP once my current packaging state is more refined.

Does this have a stable API/ABI? It seems to have a build system for a
static(-only!) library, but it's a "single-file library" primarily
designed to be vendored into larger projects. Those often don't
prioritize API stability and don't care about ABI stability at all, on
the basis that each library user is expected to vendor a known-good
version that works with the rest of their codebase.

(Prior art: the stb family, the dr_ family, libglnx, gnulib, etc.)

     smcv

Checked with abi-compliance-checker and it stays stable within the major
releases.
The build system offers the option to build the shared version as well,
so this should not pose a problem.

This would be ok to be vendored within another program/library? I
thought all vendoring is highly discouraged