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

a way to use a different directory than "nix" #172

Closed
shajra opened this issue Jan 4, 2020 · 2 comments
Closed

a way to use a different directory than "nix" #172

shajra opened this issue Jan 4, 2020 · 2 comments

Comments

@shajra
Copy link

shajra commented Jan 4, 2020

Hi!

I like niv quite a lot, but as far as I can tell, the current working directory needs to be right below a directory named "nix." If I'm wrong, then I missed something, someone can tell me show me what I'm looking for, and we can close the ticket.

Otherwise, I think it would be nicer for scripting to be able to specify with a --target DIR flag the directory where sources.json and sources.nix are to managed, with the backwards-compatible default of ./nix.

It's also kind of nicer for projects that are mostly Nix files anyway, because separating the "sources.*" files into their own "nix" directory doesn't make much sense. Specifically, I've got a Nix tutorial project where I'm trying to be very conscientious of which files are where for pedagogical/beginner-friendly reasons.

So I'm hoping this feature request isn't objectionable. I know enough Haskell to implement it. I just am knocking out a few other things first. But if someone beats me to implementing this, I won't complain 😃.

@nmattia
Copy link
Owner

nmattia commented Jan 6, 2020

It's somewhat possible currently, you can specify --sources-json (which is a file as opposed to a directory). See also #133 for directory support. I didn't get a chance to do much coding over the holidays, but I'll get back to that PR asap!

@nmattia nmattia closed this as completed Jan 6, 2020
@nmattia
Copy link
Owner

nmattia commented Jan 6, 2020

(feel free to re-open if #133 is not exactly what you're looking for!)

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

No branches or pull requests

2 participants