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.

In reply to @mrcjk:matrix.org

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.

I’ve been digging into it… and I don’t know how to solve this yet (probably because I don’t know enough about Nix yet).

The powerline plugin depends on python and the powerline module… and it has to change vim’s python sys.path. Awkwardly enough, vim’s python sys.path is different from the shell’s sys.path (vim’s one not including the path to the site-packages where the powerline module is located).

In reply to @oldaq:matrix.org

I’ve been digging into it… and I don’t know how to solve this yet (probably because I don’t know enough about Nix yet).

The powerline plugin depends on python and the powerline module… and it has to change vim’s python sys.path. Awkwardly enough, vim’s python sys.path is different from the shell’s sys.path (vim’s one not including the path to the site-packages where the powerline module is located).

From what I can tell, powerline isn't a vim plugin in the traditional sense, and it's already been packaged.

It integrates with vim, but you need to build vim with python3 support, or use neovim (which has python3 support enabled by default).

It does indeed. The simplest way to disable it is to set

nix.monitored.package = pkgs.nix-monitored.override { withNotify = false; };

In reply to @ners:nixos.dev
@room a gentle reminder that we're meeting tomorrow at 18:00! https://www.meetup.com/nix-zurich/events/299934110/

In reply to @nebucatnetzer13:matrix.org
Is it now every time on Thursday?

In reply to @ners:nixos.dev
At the moment it's about ~monthly, but I'll gladly organise whenever people are up for it. 🙂

In reply to @ners:nixos.dev
Ah, thanks for reminding me. I'll create one for 25th and 26th May.

In reply to @ners:nixos.dev
Ah, thanks for reminding me. I'll create one for 25th and 26th May.