You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it is a good idea to name-space ./pkgs overlays to avoid name clashes and for clarity throughout the repo-local usage within profiles. The name space prefix can be stripped during export.
namespacing also helps with sharing the overlay attribute, so consumers would do, after pulling in nixflk overlays from other parties:
{_=pkgs.nrdxp.broot;_=pkgs.blaggacao.exa;}
As a convention, the name spacing should map the github user. This seems sufficiently unique and in cases there are those rare name clashes, where gitea.com/blaggacao is different than github.com/blaggacao, and they clash, we can still figure out how to work arround.
This seems like an important precedent we ought to set.
But they can still do:
nix build github:nrdp/nixflk#broot (not firm on the syntax yet → pseudo exmaple)
I think it is a good idea to name-space
./pkgs
overlays to avoid name clashes and for clarity throughout the repo-local usage within profiles. The name space prefix can be stripped during export.As seen in:
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: