mirror of
https://github.com/foo-dogsquared/nixos-config.git
synced 2025-02-07 12:19:07 +00:00
8b5fd926ec
It now allows for package to use our own packages easily. Though, having a recursive attribute set can be easier, setting our package list this way is easier to maintain in the long-term since it is a set-and-forget setup. The only disadvantage I can see is the need to re-review what the hell the code is doing depending on my familiarity for Nix in the future. ;p |
||
---|---|---|
.. | ||
tic-80 | ||
default.nix | ||
doggo.nix | ||
gnome-shell-extension-burn-my-windows.nix | ||
gnome-shell-extension-desktop-cube.nix | ||
gnome-shell-extension-fly-pie.nix | ||
gnome-shell-extension-pop-shell.nix | ||
guile-config.nix | ||
guile-hall.nix | ||
junction.nix | ||
libcs50.nix | ||
llama.nix | ||
neo.nix | ||
photon-rss.nix | ||
pop-launcher-plugin-duckduckgo-bangs.nix | ||
pop-launcher.nix | ||
ratt.nix | ||
README.adoc | ||
sioyek.nix | ||
vpaint.nix |
My custom packages live here. It is setup similar to nixpkgs and my previous NUR. Thus, the conventions are similar to the package definitions in the mentioned repositories.
To build the packages…
-
With Nix pre-v2.3,
nix-build ./pkgs -A ${pkg}
. -
Nix v2.4 and enabled Nix flakes experimental feature and new CLi (e.g.,
experimental-features = nix-command flakes
),nix build .#${pkg}
.