- Don't fetch dotGit directory.
- Dot git dir gets different object packs when it is pulled from
different nixpkgs versions which causes hash mismatch.
- Patch Makefile not use git revision from .git.
Signed-off-by: Ganga Ram <Ganga.Ram@tii.ae>
Product page:
<https://www.gmktec.com/products/nucbox-g3-plus-enhanced-performance-mini-pc-with-intel-n150-processor>
This profile just configures the Intel Twin Lake N150 CPU and integrated
graphics for this mini-PC. fstrim is also enabled for the SSD. That's all this
seemed to need to function properly. As is now expected from Intel NUC systems,
it provides a solid "out-of-the-box" experience. No special quirks are apparent.
We import the Alder Lake modules since Twin Lake is just a refreshed version of
the Alder Lake-N series. Re-using those seems to be fine for this purpose.
The previous implementation was checking the kernel version through
`pkgs.linux`, which is only representative of the final system if
`boot.kernelPackages` is left as the default value of
`pkgs.linuxPackages`.
You can of course change this to other package sets, such as
`pkgs.linuxPackages_latest`. Instead, we now reference the kernel
through `config.boot.kernelPackages.kernel`.
The previous implementation was sourcing the kernel through `pkgs.linux`,
which is only representative of the final system if `boot.kernelPackages`
is left as the default value of `pkgs.linuxPackages`.
You can of course change this to other package sets, such as
`pkgs.linuxPackages_latest`. Instead, we now reference the kernel
through `config.boot.kernelPackages.kernel`.
The previous implementation was checking the kernel version through
`pkgs.linux`, which is only representative of the final system if
`boot.kernelPackages` is left as the default value of
`pkgs.linuxPackages`.
You can of course change this to other package sets, such as
`pkgs.linuxPackages_latest`. Instead, we now reference the kernel
through `config.boot.kernelPackages.kernel`.
The previous implementation was checking the kernel version through
`pkgs.linux`, which is only representative of the final system if
`boot.kernelPackages` is left as the default value of
`pkgs.linuxPackages`.
You can of course change this to other package sets, such as
`pkgs.linuxPackages_latest`. Instead, we now reference the kernel
through `config.boot.kernelPackages.kernel`.