https://github.com/divnix/devos/blob/main/flake.nix has a bit that refers to core at line 126: base = [ core users.nixos users.root ];

what is that core and where is it defined?

I try to enter nix-shell in my devos folder and get error: attribute 'cw' missing, at /nix/store/... which is the middle line here:

            suites = with profiles; rec {
              base = [ core users.cw users.root ];
            };

my user is defined in users/cw/default.nix so it should be raked in. any ideas?

In reply to @cw:kernelpanic.cafe
no!

In reply to @kraftnix:matrix.org

hey all, is anyone having issues with the latest digga where the deploy flake input is no longer following digga's nixpkgs.follows when using deploy.follows = "digga/deploy in a devos-like setup?

not sure if I explained that well, basically since updating from a55450a16d362b6e1c50bb4025aaa604b385d3ba to latest on main, I suddenly have a duplicated nixpkgs which only deploy uses.

At work I learned that the follows inputs are not completely gone and that the only really effective way is to reduce & push to the leave:

• reduce -> don't bother about non-nixpkgs, since they are usually libs, are small and don't have huge deps themselves
• push to the leaf: make it a responsability of the end user flake. (Almost) all follows issues that I still hace seen with recent versions could be resolve when the follows statements are used at the leaf.

In reply to @blaggacao:matrix.org

At work I learned that the issues with follows inputs are not completely gone and that the only really effective way to deal with it (for now) is to reduce & push to the leave:

• reduce -> don't bother about non-nixpkgs, since they are usually libs, are small and don't have huge deps themselves
• push to the leaf -> make it a responsability of the end user flake. (Almost) all follows issues that I still hace seen with recent versions could be resolve when the follows statements are used at the leaf.

In reply to @blaggacao:matrix.org
At this point, my current best advice to reduce closure size is to fare with a balanced approch: deduplicate the core blobs like nixpkgs and make sure you don't have largely duplicated dep trees, but don't care too much about leaf packages with only a few runtime deps & don't care at all about pure nix libraries.

In reply to @blaggacao:matrix.org
Btw, I kicked bud out of my own env, since I really like the uniformity that deploy-rs provides for the current use cases of bud.