How to override options of an already wrapped package?

[jla2000]

I have created a wrapped version of git using 'wrap', but I want to override the username/email afterwards. How can this be achieved?

[BirdeeHub]

Call .wrap again! The package has that too! You can call it as many times as you wish.

https://birdeehub.github.io/nix-wrapper-modules/md/getting-started.html#extending-configurations

You always have access to .wrap, .apply, .eval, and .extendModules, which are all aliases for .extendModules with very slightly different behavior (for convenience, usually .wrap is the easiest as it then grabs the package from the result, unless you cannot pass it a pkgs yet). They are present as read only values in config, as well as in passthru on the final package, which you can access from top level on the resulting package like thepackage.wrap { ??? } or thepackage.wrap ({ pkgs, ... }: { ??? }) or even thepackage.wrap [ {} ({...}: {}) ] actually.

You may need to use lib.mkForce in the second call to override the values you set, as the module system dictates, unless you set them with lib.mkDefault in your base module, then you could just set them!

So, in this case, where you set it in your base module without using lib.mkDefault, your_wrapped_git.wrap { settings.user.name = lib.mkForce "a new name"; } would be necessary to override the name.

Things like lib.types.listOf, lib.types.attrsOf, and lib.types.lines merge across calls and so will not need lib.mkForce, others are a single value which likely will not. This is a feature of the module system. It will tell you if you need lib.mkForce or not. It works just like it was another module appended to your original call to evalModules

In this way, you can even make options for yourself using options.someoption = lib.mkOption {...}; like any other type of module, specifically for the purpose of overriding it in one of your configs but not other ones. And then set it in a later call to .wrap in the appropriate config. And then, once you have set that value once, you aren't even stuck with it! This is often very useful for stylix colors.

[jla2000]

Thanks for the response 😃 I was trying to to it like this but it didnt work, but it turned out it was due to some stale package.

Calling wrap twice does the trick :D

[BirdeeHub]

I believe you can use lib.highPrio in the environment.systemPackages or home.packages to make sure a package would win over another one with the same paths? I think you can lib.mkBefore too.

One of those should help in making sure the wrapped one wins if it was installed by some other thing as well. But, of course the most obvious (and usual) way would just be to make sure that the wrapped one is the only version of it installed.

[jla2000]

The reason was that I just removed home-manager and replaced everything with wrapped packages in systemPackages, but the stuff from home-manager was still being sourced and took precendence over the new packages xD After removing stale home-manager links it worked as expected