I started another iteration of implementing the game of life with nix, this time using nix-unit.

I’m kind of lost.

Can someone provide a repo with a “add” function and a simple test, so I have a structure and understand better how to work with nix-unit?

nix flake init "github:mrcjkb/flakes#nix-unit"

nix flake init -t "github:mrcjkb/flakes#nix-unit"

I'm trying to package some proprietary garbage with buildFSHEnv[Bubblewrap]. It expects to be able to create a license file in /opt/<pkg-name>.

Does anyone have some pointers that could help me figure out to get this working?

This is what I have so far:

# in mkDerivation
  installPhase = ''
    cp -r ./ $out/
    ${buildFHSEnvBubblewrap {
      name = "falconctl";
      runScript = "$out/opt/CrowdStrike/falconctl";
      extraBwrapArgs = ["--bind $out/opt /opt"];
    }}/bin/falconctl -s --cid=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
  '';

And then, with another wrapper:

  falcond = buildFHSEnvBubblewrap {
    name = "falcond";
    targetPkgs = pkgs: [falcon-sensor-unwrapped libnl openssl];
    runScript = "${falcon-sensor-unwrapped}/opt/CrowdStrike/falcond";
    extraBwrapArgs = [
      "--bind \"$HOME\"/.local/share/CrowdStrike/falconstore ${falcon-sensor-unwrapped}/opt/CrowdStrike/falconstore"
    ];
  };

I'm working on a nixos module where the systemd service copies the falconstore file from the -unwrapped package to the .local/share location.

Is there a reason why there is no powerline vim plugin?

Defining one looks almost as easy as:

pkgs.vimUtils.buildVimPlugin {
  name = “powerline”;
  src = “${pkgs.powerline}/share/vim”;
}

(Well… of course… there is some more to it, since we depend on python etc.)

But maybe there’s something which I am missing and it’s totally unnecessary to use buildVimPlugin.

What is your approach?

In reply to @oldaq:matrix.org

Is there a reason why there is no powerline vim plugin?

Defining one looks almost as easy as:

pkgs.vimUtils.buildVimPlugin {
  name = “powerline”;
  src = “${pkgs.powerline}/share/vim”;
}

(Well… of course… there is some more to it, since we depend on python etc.)

But maybe there’s something which I am missing and it’s totally unnecessary to use buildVimPlugin.

What is your approach?

Plugins that can't be generated with the updater need to be added manually (see for example vim-clap) or, if they just need something added on top of the generated nix, overridden.

As for why it hasn't been added yet. There probably just hasn't been a nix user who uses the plugin yet.