rarias/jungle
2
0
Fork 3
Code Issues 57 Pull Requests 7 Actions Packages Projects Releases Wiki Activity

Add quickShell to build devshells quickly #209

Closed
abonerib wants to merge 1 commits from abonerib/jungle:quick-shell into master
pull from: abonerib/jungle:quick-shell
merge into: rarias:master
Conversation 3 Commits 1 Files Changed 2 +77
abonerib commented 2025-10-28 16:57:03 +01:00
Collaborator
Copy Link

This is the same I built in: https://github.com/Leixb/quick-nix

But I think it'll be better to have it in sync with jungle instead of having to update the flake lock.

I am probably the only one that will use it.

This is the same I built in: https://github.com/Leixb/quick-nix But I think it'll be better to have it in sync with jungle instead of having to update the flake lock. I am probably the only one that will use it.
abonerib added 1 commit 2025-10-28 16:57:04 +01:00
Add quickShell to build devshells quickly
All checks were successful
CI / build:cross (pull_request) Successful in 6s
Details
CI / build:all (pull_request) Successful in 18s
Details
9deef256a2
rarias commented 2025-10-30 11:09:10 +01:00
Owner
Copy Link

Not sure if your use case can be satisfied by #211. If so, I would prefer generating a flake.nix on disk so we can go back to the same shell in the future, rather than generating it on the fly but never recording it on disk.

Not sure if your use case can be satisfied by https://jungle.bsc.es/git/rarias/jungle/pulls/211. If so, I would prefer generating a flake.nix on disk so we can go back to the same shell in the future, rather than generating it on the fly but never recording it on disk.
abonerib commented 2025-10-30 16:46:20 +01:00
Author
Collaborator
Copy Link

Not sure if your use case can be satisfied by #211. If so, I would prefer generating a flake.nix on disk so we can go back to the same shell in the future, rather than generating it on the fly but never recording it on disk.

I see this more akin to a combination of nix develop + shell where the user is fine with an ephemeral shell.

> Not sure if your use case can be satisfied by https://jungle.bsc.es/git/rarias/jungle/pulls/211. If so, I would prefer generating a flake.nix on disk so we can go back to the same shell in the future, rather than generating it on the fly but never recording it on disk. I see this more akin to a combination of `nix develop + shell` where the user is fine with an ephemeral shell.
rarias commented 2025-10-31 11:18:00 +01:00
Owner
Copy Link

I see this more akin to a combination of nix develop + shell where the user is fine with an ephemeral shell.

I don't want to allow ephermeral shells without the flake.nix and flake.lock, as they make it hard to reproduce a problem that happens later on.

We can reduce the friction in nixgen to generate the shell by calling nix develop at the end, and maybe finding a way to automatically store the flake.nix and flake.lock somewhere safe in such a way that can be dumped from inside the shell. Let me know if that would suit your use case.

> I see this more akin to a combination of `nix develop + shell` where the user is fine with an ephemeral shell. I don't want to allow ephermeral shells without the flake.nix and flake.lock, as they make it hard to reproduce a problem that happens later on. We can reduce the friction in `nixgen` to generate the shell by calling `nix develop` at the end, and maybe finding a way to automatically store the flake.nix and flake.lock somewhere safe in such a way that can be dumped from inside the shell. Let me know if that would suit your use case.
abonerib closed this pull request 2026-01-21 12:38:29 +01:00
All checks were successful
CI / build:cross (pull_request) Successful in 6s
Details
CI / build:all (pull_request) Successful in 18s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
ceph
ci
config
cross
hw
io
kernel
mpi
net
nix
ops
repair
slurm
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
abonerib arocanon varcila rarias
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: rarias/jungle#209
Delete Branch "abonerib/jungle:quick-shell"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?