[–] [S] 5 points 4 weeks ago

Fair point) It really depends on how you use your system. If I weren't constantly tweaking things, I don't think it'd be an issue for me either.

In my case I also use Home Manager as a NixOS module, so every home config change is a system rebuild too, and I'm at almost a thousand generations by now. When I'm trying out something new I can hit up to 50 rebuilds in a day (rare, but it happens), and that's exactly when it becomes a problem.

So yeah, for a lot of people this is definitely overkill, but for others (similar to how I use it) it can save a lot of digging.

  • source
  • parent
  • context
  • [–] 7 points 4 weeks ago (1 child)

    never really had the issue where I don't know what commit is tied to what generation. add to the fact I might roll back once in a blue moon and if it does require a roll back I already know why I have to roll back.

    That being said this is neat, I like it, but I think it's overblown for a minimal issue.

  • source
  • [–] 4 points 4 weeks ago

    If you want something similar to hyprland, but easier syntax similar to the old hyprlang before they switched to lua, you can try MangoWC. Has pretty much all the eye candy and features too

  • source
  • [–] 11 points 1 month ago (4 children)

    I’m using Niri+Noctalia to my satisfacion, but I’m coming from Sway so the system feels familiar. I am not aware of any scandals, but I haven’t gone and checked, so…

  • source
  • [–] 5 points 1 month ago (1 child)

    Hyprland is not the right choice. If you're not aware, it's a fascist aligned project. It's your call if that's an issue for you personally or not, but people will probably not be able to assist with it much.

  • source
  • [–] 2 points 1 month ago

    I just installed it yesterday after seeing it recommended on the Nix wiki, but I didn't know a fellow Lemmy user is the dev behind it! The only features I need that aren't present so far are automatic mod dependency resolution and modpacks.

  • source
  • [–] 2 points 1 month ago* (1 child)

    I would've thought that running switch again would put things back. But I might be able to help you out by sharing the structure of symlinks I have on my machine.

    First, a couple of ideas to try. You probably lost your Nix user profile state in addition to Home Manager state. According to my searching I think some Nix commands should recreate the profile links for you. Try running nix profile list and see if that puts anything back in ~/.local/state/nix/profiles/. If it does that might get you to a point where running switch will get you going again.

    Another idea: Home Manager generations have store paths that look like this:

    /nix/store/0k18msqsz0cdh751a9nv3grvfg8ajn2q-home-manager-generation
    

    Each of those has an executable called activate. Running one of those might get you set up again - possibly in a pretty old generation. I think that's a procedure you can normally use to roll back to a previous generation. I'd find a store path ending in home-manager-generation, and give it a go.

    I have ~/.nix-profile linked to /home/jesse/.local/state/nix/profiles/profile. I believe that's the Nix / NixOS user profile rather than Home Manager specifically, but I think that's an important piece.

    You're probably aware, but you can recreate that and other links with commands like ln -s $HOME/.local/state/nix/profiles/profile $HOME/.nix-profile.

    My Nix state in .local is in ~/.local/state/nix/profiles/ which has content like this:

    home-manager -> home-manager-229-link
    home-manager-227-link -> /nix/store/74awmvpikhvhi3rgn8c9iznvyc6fdi9j-home-manager-generation
    home-manager-228-link -> /nix/store/w2bcxdvi5ak3rbqkpjzksgrk02xvkzsr-home-manager-generation
    home-manager-229-link -> /nix/store/nfngszmd3yi9i0r5mkmy56yavjsxxv3a-home-manager-generation
    profile -> profile-290-link
    profile-288-link -> /nix/store/pcjlhf0m8iprnglvfv5mwi6rf41yqrfd-user-environment
    profile-289-link -> /nix/store/zq3lh6hr8nbm3n15avqcdjv7rlzaqr25-user-environment
    profile-290-link -> /nix/store/skfbszbmc7b7i55rj91zqi9r9vv2c59a-user-environment
    

    So that's both Home Manager generations, and Nix user profile generations. All symlinks, or symlinks to symlinks. I don't know if the generation number is stored in state somewhere. You might be able to pick an arbitrary number, pick an arbitrary home-manager-generation store path, and create the corresponding chain of two symlinks.

  • source
  • [–] 5 points 1 month ago (1 child)

    Oh, the Minecraft launcher? Neat! I remembered after a couple of minutes of wondering what I'm looking at that I do use that launcher, and it could be more Nix friendly! Even avoiding the manual java install path update when java updates in nixpkgs would be helpful.

  • source
  • [–] 3 points 1 month ago

    This is great; I've been waiting for this to be picked up for a while. The only thing Prism now lacks is application-layer sandboxing for Java mods, whose importance was shown post-Fracturizer. Perhaps this is something that could be done with Nix too, with a runtime injection into the mods' prologues that interfaces with a shared coremod library. The principal issue with this approach would be JRE privilege escalation requirements. But this is putative, and I'm glad this project targets a few steps that would otherwise be preliminary.

  • source
  • [–] [S] 4 points 1 month ago

    I also wrote nix package and module mirror-git which can help you mirror a git repo either locally or to another source forge (SSH support).

    There are alternatives of course e.g hosting your own forgejo or gitlab instance and enabling mirroring of remote repositories.

  • source
  • [–] 5 points 1 month ago (1 child)

    If antigravity doesn't work on stable I suggest that you remove the inputs.nixpxgs.follows = "nixpkgs" line so that antigravity uses the package set from its own lock file. Nix is especially good at tolerating multiple package sets / dependency versions on the system. The main drawback is you'll download more, and use more disk space.

    If it doesn't work you can undo by reverting the changes to flake.nix to switch back to unstable and to put that line back. Then rebuild. If you want to get back to exactly the same state as before then also revert changes to flake.lock.

    If you're used to other distros you might be used to package manager operations making changes you can't undo. That doesn't happen on NixOS - you can undo pretty much anything. Even if you get an unbootable system, you can select the previous generation from the boot menu. The best thing about NixOS is experimenting with few consequences!

  • source
  • parent
  • context
  • view more: ‹ prev next ›