Looking at https://pkgs.alpinelinux.org/packages, almost every single package in Alpine Linux is versioned as
d are numbers,
d is the "patch release" of the version
As the name implies, I suppose the patch release is a bug or security fix.
What about the licensing of the package? Is it possible that the license of a package is changing within a patch release, or can we ensure that the license is always the same within for a fixed
a.b.c version, whatever
Background is legal compliance: when we deliver a software based on Alpine Linux (delivered as Docker container), we need to ensure that the license of every single component is properly defined and delivered with our software.
But "clearing" a component requires getting the source code, and is always time consuming. I see here how to get the exact source code of a package, but this is much more complex that getting just the tag of the related GitHub repository.
So for compliance purposes, if the license remains the same, I would like to take any package of version
a.b.c and ignore the release patch. What do you think?