source/.envrc

# This way "import <snapshot>" means to use vendored nixpkgs snapshot anywhere in
# this repository, no matter how deep inside subdirectory tree it is. Alternative of
# using "import ../../." (with correct amount of "..") makes moving things around more
# complicated.
#
# Not something one need to do every day, but still. Ergonomics matters.
export NIX_PATH=snapshot=$PWD:nixpkgs=$PWD/nixpkgs

# vim:ft=bash:
text/gemini: use /nixpkgs for building shell environment One of benefits of mono-repository is that it makes it easier to make things consistent. Instead of each repository component using its own nixpkgs snapshot, we can use single snapshot to reduce amount of duplication and rebuilds. 2023-07-23 01:31:58 +00:00			`# This way "import <snapshot>" means to use vendored nixpkgs snapshot anywhere in`
			`# this repository, no matter how deep inside subdirectory tree it is. Alternative of`
			`# using "import ../../." (with correct amount of "..") makes moving things around more`
			`# complicated.`
			`#`
			`# Not something one need to do every day, but still. Ergonomics matters.`
treewide: Make sure "import <nixpkgs> {}" works It seems that this expression is used somewhere in internals of nixpkgs itself, and some stuff not working otherwise. I didn't debug it thorously, but it helped me to get "nix-shell" for "haskell/large-anon" working. 2023-09-25 20:02:29 +00:00			`export NIX_PATH=snapshot=$PWD:nixpkgs=$PWD/nixpkgs`
text/gemini: use /nixpkgs for building shell environment One of benefits of mono-repository is that it makes it easier to make things consistent. Instead of each repository component using its own nixpkgs snapshot, we can use single snapshot to reduce amount of duplication and rebuilds. 2023-07-23 01:31:58 +00:00
			`# vim:ft=bash:`