Skip to content
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

Add info about creation of flake.nix #84

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ShalokShalom
Copy link

Until, there was no info about the name, path or existence of the flake.nix
I am a newbie myself, so if I have messed this up, please be gentle. 🙂

@r-vdp
Copy link
Member

r-vdp commented Apr 21, 2024

I don't think that these are the right suggestions, flakes should not live in privileged locations, it makes more sense to define the flake in some git clone of the repo where you'll keep this code. In general it is up to the user to decide where to store this file.

Also, the following section describes what to put in the flake file, which I think makes it rather clear what to do.

This project is an MVP currently and although it's usable for what it can currently do, it is probably not really appropriate for people new to nix.

@ShalokShalom
Copy link
Author

Thanks a lot for answering so swiftly 🙂

I literally asked the Matrix channel, and multiple people told me, flakes can live where they want. And that the mentioned paths are good, cause they live together with other Nix files there.

I am packaging this, so that is why "I have to decide for the user" where this is going to be.
So I will choose a place next to the home directory, I guess.

@r-vdp
Copy link
Member

r-vdp commented Apr 22, 2024

Yeah, I personally feel that they should not be root-owned, that just encourages using sudo for everything all the time.

@r-vdp r-vdp marked this pull request as draft April 23, 2024 08:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants