Support esoteric use cases by giving control over whether pre- or post-
release components are added to the rendered pin, or more
straighforwardly, allow 'v' or 'V' to be used to expand the base version
or full version of the target package, respectively.
For example, say you want to create an install requirement that will
exactly match the version of a package used at build time. Using
fromBuildEnv: true does not do that. Using fromBuildEnv: ==x.x.x
does not render any pre- or post-release components. Now it is possible
to put fromBuildEnv: ==V which would render into, e.g., ==1.2.3+r.1.
Support esoteric use cases by giving control over whether pre- or post- release components are added to the rendered pin, or more straighforwardly, allow 'v' or 'V' to be used to expand the base version or full version of the target package, respectively.
For example, say you want to create an install requirement that will exactly match the version of a package used at build time. Using
fromBuildEnv: truedoes not do that. UsingfromBuildEnv: ==x.x.xdoes not render any pre- or post-release components. Now it is possible to putfromBuildEnv: ==Vwhich would render into, e.g.,==1.2.3+r.1.