Hardware/TUXEDO: Difference between revisions
imported>Mohe2015 m Fix typo |
imported>Dafitt mNo edit summary |
||
Line 67: | Line 67: | ||
As noted in an issue on the project's GitHub page<ref>'''Build broken on nixos-unstable #5''', Nov 13, 2022 - https://github.com/blitz/tuxedo-nixos/issues/5</ref>, blitz's TCC distribution is tested exclusively against Nixpkgs 22.11; as such, there might be errors when building it after overriding its Nixpkgs version to a newer one. | As noted in an issue on the project's GitHub page<ref>'''Build broken on nixos-unstable #5''', Nov 13, 2022 - https://github.com/blitz/tuxedo-nixos/issues/5</ref>, blitz's TCC distribution is tested exclusively against Nixpkgs 22.11; as such, there might be errors when building it after overriding its Nixpkgs version to a newer one. | ||
To avoid such problems, it can be useful to delete the <source lang="nix" enclose="none">inputs.nixpkgs.follows = "nixpkgs";</source> line in the example above and to specify <source lang="nix" enclose="none">tuxedo-control-center.package = tuxedo-nixos.packages.x86_64-linux.default;</source> right after the enable instruction. Doing this, in fact, will build the TCC against the Nixpkgs version it is meant to. | To avoid such problems, it can be useful to delete the <source lang="nix" enclose="none">inputs.nixpkgs.follows = "nixpkgs";</source> line in the example above and to specify <source lang="nix" enclose="none">hardware.tuxedo-control-center.package = tuxedo-nixos.packages.x86_64-linux.default;</source> right after the enable instruction. Doing this, in fact, will build the TCC against the Nixpkgs version it is meant to. | ||
== Tuxedo Keyboard == | == Tuxedo Keyboard == |