Found out the version of neovim on PopOS was fairly outdated, and I would like to use more recent versions. So I am confronted with these choices : Do I go for PPAs, or is distrobox fine for this purpose? While distrobox works well, I am worried that mismatches in packages could cause issues.

About flatpak: it is a no-go for me in this usecase, since it takes quite a bit of configuration to “escape” the sandbox.

    • someacnt_@lemmy.worldOP
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      8 months ago

      Yeah, just tried and there were no issues with dependencies. However, it seems like language servers are not working well. Gotta see how much of a hassle it is to go through it. EDIT: It was missing gcc, installed it and it works! It was less hassle than I expected, thank you!!

  • ksp@sh.itjust.works
    link
    fedilink
    arrow-up
    5
    ·
    8 months ago

    I’be been having the same issue on mint, I did build it from source but it’s not the most convenient. I did afterwards use a fedora atomic (immutable) and a distrobox with fedora classic on it. I think it is the most convenient if you are ready to use containers. You will have to export it to the host and it will use the configuration from your home folder

    If I remember well, the PPA is outdated too !

  • Shareni@programming.dev
    link
    fedilink
    arrow-up
    3
    arrow-down
    1
    ·
    8 months ago

    I’d suggest nix and home-manager. I just added the following to my home.nix, and lazyvim works perfectly fine on nvim 0.9.5 (0.9.4 on the stable branch):

      home.packages = with pkgs;
        ([
           ...
          #neovim
          #git,make,npm,node,and ripgrep are already installed
          neovim
          python311
          python311Packages.pip
          # python311Packages.pynvim
          luajitPackages.luarocks
          cargo
          # lunarvim
          lazygit
          tree-sitter
          nerdfonts
          ....
        ]);
    
    • someacnt_@lemmy.worldOP
      link
      fedilink
      arrow-up
      5
      ·
      8 months ago

      I tried that, but

      1. It requires more configuration, the executable was not able to recognize lua-5.1 out-of-the-box.
      2. This approach excludes auto-updates.