Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

name space ./pkgs overlays #60

Closed
blaggacao opened this issue Dec 30, 2020 · 1 comment
Closed

name space ./pkgs overlays #60

blaggacao opened this issue Dec 30, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@blaggacao
Copy link
Contributor

blaggacao commented Dec 30, 2020

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.

@blaggacao blaggacao changed the title name space ./pkgs overrieds name space ./pkgs overrides Dec 30, 2020
@blaggacao blaggacao changed the title name space ./pkgs overrides name space ./pkgs overlays Dec 30, 2020
@blaggacao
Copy link
Contributor Author

blaggacao commented Dec 30, 2020

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)

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants