/explore
|
You are here 
|
nguyenhuythanh.com | ||
| | | | |
agentultra.com
[AI summary] A technical deep-dive into resolving symbol clashing (specifically the 'sin' IFUNC symbol) when calling a Zig-compiled C library from a Haskell application. |
|
| | | | | ||
| | | | |
kalbas.it
We use Nix, a reproducible package manager, to provide a fixed environment with Hugo and the Hugo theme we want to use. This method does not require us to copy the theme into our repository or to add it as a submodule. |
|
| | | | | ||
| | | | |
rgoswami.me
A short exploration of multi-user nix and interacting with the Nix User Repository without root Background For multi-user nix installations1, the NIX_PATH variable is empty. Here I briefly go over two approaches to mitigate this, one with nix-channel and the other by manual pinning. Note that this post will eventually be superseded for most cases by a better flake workflow. Channels The idea behind using a channel is essentially that the tar at a particular commit / tag will be downloaded and stored, typically at $HOME/.nix-defexpr/channels. This is in-fact a symlink typically as seen below. |
|
| | | | | ||
| | | | |
daniel-siepmann.de
Interested in a declarative way to describe your user environment on macOS / Linux systems? This post explains my transition to nix and home-manager to achieve the goal. |
|
| | | |||
