-
Notifications
You must be signed in to change notification settings - Fork 54
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
profiles #16
Comments
FWIW, I got the term "profiles" directly from the nixpkgs module directory where it is already being used in this fashion. |
I am quite a fan of the name Also, may I add that I've seen several repos with |
Hm, @gytis-ivaskevicius that does not solve my (our) problem. Would you care and try to find a negotiated consensus solution? From devos' perspective, there are no alternative namings available. We are trying to catch the same trout, here. 👎 for closing. 😉 One obvious suggestion would be either Both would preserve upstream usage semantics of the single word "profiles".
We would care less how people actually name their folders. The goal is to wrap As I had understood it the goal of |
Alright, this will be fixed using the name |
Thank you! Much appreciated. 👍 |
nixosProfiles might conflict a little too much with downstream naming.
nixosProfiles might conflict a little too much with downstream naming.
closed in #20 |
flake-utils-plus/systemFlake.nix
Line 9 in 51cb739
nixosProfiles
do contain system profiles, in a sense, but more accurately they contain host configs.This clashes with devos' usage of the term
profiles
which is reserved for a very special meaning:With
fup
reserving the name, we might have a problem finding an alternative naming scheme. (and also it's somewhat established, already)/cc @Pacman99
The text was updated successfully, but these errors were encountered: