I have a use case where it would be handy to use semantic versioning in the context of being a packager, or someone who repackages the work of others to make patches or customizations.
Also, in my own use case, I am creating patched versions of container images, wherein a specific upstream image release is modified to have the latest packages versions installed from the package manager.
Are there restrictions for someone who would like to use semantic versioning in this context?
Originally created by @tspearconquest on GitHub (Jun 24, 2021).
Original GitHub issue: https://github.com/semver/semver/issues/715
Hello,
I have a use case where it would be handy to use semantic versioning in the context of being a packager, or someone who repackages the work of others to make patches or customizations.
Also, in my own use case, I am creating patched versions of container images, wherein a specific upstream image release is modified to have the latest packages versions installed from the package manager.
Are there restrictions for someone who would like to use semantic versioning in this context?
I think all of the SemVer maintainers are packaging tool owners. I would be willing to bet a box of donuts that at least 90% of all SemVer use cases, involve some sort of packaging tool. We don't actually version API's in most cases, what we version is the package that contains the API, so we're really versioning packages in the vast majority of instances.
<!-- gh-comment-id:981308109 -->
@jwdonahue commented on GitHub (Nov 29, 2021):
I think all of the SemVer maintainers are packaging tool owners. I would be willing to bet a box of donuts that at least 90% of all SemVer use cases, involve some sort of packaging tool. We don't actually version API's in most cases, what we version is the package that contains the API, so we're really versioning packages in the vast majority of instances.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @tspearconquest on GitHub (Jun 24, 2021).
Original GitHub issue: https://github.com/semver/semver/issues/715
Hello,
I have a use case where it would be handy to use semantic versioning in the context of being a packager, or someone who repackages the work of others to make patches or customizations.
Also, in my own use case, I am creating patched versions of container images, wherein a specific upstream image release is modified to have the latest packages versions installed from the package manager.
Are there restrictions for someone who would like to use semantic versioning in this context?
@jwdonahue commented on GitHub (Nov 29, 2021):
I think all of the SemVer maintainers are packaging tool owners. I would be willing to bet a box of donuts that at least 90% of all SemVer use cases, involve some sort of packaging tool. We don't actually version API's in most cases, what we version is the package that contains the API, so we're really versioning packages in the vast majority of instances.