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

Should document that for --lein you need LEIN_HOME directory #64

Open
JonathanLorimer opened this issue Jul 6, 2023 · 5 comments
Open

Comments

@JonathanLorimer
Copy link

I am creating a deps lock file via a nix derivation, and since it is sand-boxed LEIN_HOME is not defined.

@JonathanLorimer JonathanLorimer changed the title Should document that for --lein you need LEIN_HOME Should document that for --lein you need LEIN_HOME directory Jul 6, 2023
@jlesquembre
Copy link
Owner

Do you mean you are running the deps-lock CLI in a nix build? That isn't supported, since we need network access to generate the lock file.

@JonathanLorimer
Copy link
Author

You can run it in a nix build via fixed output derivations!

@jlesquembre
Copy link
Owner

jlesquembre commented Jul 6, 2023

You can run it in a nix build via fixed output derivations!

good point, never though about it.

I wonder if we could use that trick to include clj-nix packages on nixpkgs 🤔

@JonathanLorimer
Copy link
Author

You can run it in a nix build via fixed output derivations!

good point, never though about it.

I wonder if we could use that trick to include clj-nix packages on nixpkgs thinking

We definitely could!

@jlesquembre
Copy link
Owner

I really like how you are generating the lock file in a derivation:

https://github.com/JonathanLorimer/maelstrom.nix/blob/a45550468f66e776d250f6e88ae000d17da306a9/flake.nix#L27-L46

With it, if I upstream clj-nix to nixpkgs, we don't need to commit the lock files, while at the same time we can share the input dependencies between different derivations

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