New nix flake for development purposes #920
No reviewers
Labels
No labels
Blocked
Bug
Documentation
Duplicate
Enhancement
Good first issue
Help wanted
Idea
In progress
Invalid
Major feature set
Packaging
Question
Soon
UI/UX
Upstream
You're dreamin'
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nostr/gossip!920
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "majje/nix-develop"
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?
Hi Mike
I tried to use the flake.nix in your repository but it didn't help me to setup a development shell. Your flake is probably used to create a nix package and it is using an nixos-23.11, and it failed with:
My flake should probably be mixed with the original flake, without breaking any existing functionality, but I'm no nix/nixos expert, so I just don't know how :-(
Before merging, at least have some nix expertise looking at it... (Maybe @Kodylow can have a look)
I got inspiration from https://drakerossman.com/blog/rust-development-on-nixos-bootstrapping-rust-nightly-via-flake
To build and run:
Thanx for a great nostr client!
I did not create the flake file in the gossip repo, and I had half a mind to not allow it because I have no way to verify that it even makes sense or perhaps contains hacks or something (I don't believe it does, but I can't vouch for it).
I totally understand! It was just useful to me and wanted to share.
Actually, I almost wrote that my pull request probably should not be merged ;-P
(Hopefully someday I understand how to update this https://github.com/NixOS/nixpkgs/blob/nixos-24.05/pkgs/by-name/go/gossip/package.nix)
Close it! Thanx!
Id prefer if you and @Kodylow came up with a flake file that works for both of you and I'll merge it... since we already have a flake file and it sounds like it might be wrong.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.