package dkml-component-staging-opam64
- Overview
- No Docs
You can search for identifiers within the package.
in-package search v0.2.0
Install
Authors
Maintainers
Sources
sha256=0c87a32663eaa7c6b603817b2fa57d209e795ea3573b35042d78a0cab1260667
sha512=596088a892e84c1b6473502606a4840b22f87aa9ee6f7db0617aeef7c19f87bb3df0c5a27b3083b9f15805173b04ff11f5cfb0724db9674973916ab31d8509c6
Description
For 64-bit capable platforms, opam, opam-putenv and opam-installer will be in /staging-files/. But for any platform that does not support 64-bit, this package will install nothing (aka. be a no-op). Consumers of the component should place both tools/opam64 and tools/opam32 into the PATH, so that whichever is available can be used.
Cross-compiling to both darwin_arm64 and darwin_x86_64 platforms are supported on macOS when you have both dkml-base-compiler and conf-dkml-cross-toolchain installed in your switch.
The package version, and what [opam --version] returns, are closely associated with the Opam version from the Opam source code. The only modifications are to ensure that the package version can be ordered using semver. In particular:
- 2.2.0~alpha~dev -> 2.2.0~alpha0~20221231
- 2.2.0~alpha~1 -> 2.2.0~alpha1~20230601
- 2.2.0 -> 2.2.0
The dates (YYYYMMDD) are the Git commit dates in the Opam source code, and simply replacing the tildes (~) with dashes (-) is sufficient to be a semver version.