Switch to specifying the Kernel compatibility in the same form as in the ZFS source’s `META` file. This then allows checking it against what’s in `META` to remove the need to manually check, and so reduce the cognitive load and change of mistakes when performing updates. As the “max” version is indeed a compatible version, we need to increment that for the comparison when using `versionOlder`. One side-effect here is that it makes it not possible to override the specified compatibility. We will “fix” this soon.
33 lines
916 B
Nix
33 lines
916 B
Nix
{
|
|
callPackage,
|
|
nixosTests,
|
|
...
|
|
}@args:
|
|
|
|
callPackage ./generic.nix args {
|
|
# You have to ensure that in `pkgs/top-level/linux-kernels.nix`
|
|
# this attribute is the correct one for this package.
|
|
kernelModuleAttribute = "zfs_unstable";
|
|
|
|
kernelMinSupportedMajorMinor = "4.18";
|
|
kernelMaxSupportedMajorMinor = "6.15";
|
|
|
|
# this package should point to a version / git revision compatible with the latest kernel release
|
|
# IMPORTANT: Always use a tagged release candidate or commits from the
|
|
# zfs-<version>-staging branch, because this is tested by the OpenZFS
|
|
# maintainers.
|
|
version = "2.3.3";
|
|
# rev = "";
|
|
|
|
tests = {
|
|
inherit (nixosTests.zfs) unstable;
|
|
};
|
|
|
|
hash = "sha256-NXAbyGBfpzWfm4NaP1/otTx8fOnoRV17343qUMdQp5U=";
|
|
|
|
extraLongDescription = ''
|
|
This is "unstable" ZFS, and will usually be a pre-release version of ZFS.
|
|
It may be less well-tested and have critical bugs.
|
|
'';
|
|
}
|