Issues I had:

1. Does not set NIX_PATH so you need to manually configure it so that nix-command stuff works|
2. I really don't like the fact that it has a "global" default nixpkgs instance, then you can override per-machine. It makes the hive attrset really anoyying to make modular
3. Cross-compilation is not first-class even though it definitely could be
4. When applying locally the output is just worse than nom which I don't like

Issues I had:

1. Does not set NIX_PATH so you need to manually configure it so that nix-command stuff works|
2. I really don't like the fact that it has a "global" default nixpkgs instance, then you can override per-machine. It makes the hive attrset really annoying to make modular
3. Cross-compilation is not first-class even though it definitely could be
4. When applying locally the output is just worse than nom which I don't like

you can at least work around 4 a little bit by having colmena set up the eval and then using nom directly, though you then have to colmena apply afterwards (which evals again). we just have a default.nix with

let
  pins = import ./npins;
  eval = import "${pins.colmena}/src/nix/hive/eval.nix" { rawHive = import ./hive.nix; };
in
eval.toplevel

you can at least work around 4 a little bit by having colmena set up the eval and then using nom directly, though you then have to colmena apply afterwards (which evals again). we just have a default.nix with (below, and then use nom build -f . [system name]

let
  pins = import ./npins;
  eval = import "${pins.colmena}/src/nix/hive/eval.nix" { rawHive = import ./hive.nix; };
in
eval.toplevel

you can at least work around 4 a little bit by having colmena set up the eval and then using nom directly, though you then have to colmena apply afterwards (which evals again). we just have a default.nix with (below), and then use nom build -f . [system name]

let
  pins = import ./npins;
  eval = import "${pins.colmena}/src/nix/hive/eval.nix" { rawHive = import ./hive.nix; };
in
eval.toplevel

you can at least work around 4 a little bit by having colmena set up the eval and then using nom directly, though you then have to colmena apply afterwards (which evals again). we just have a default.nix with (below, for a non-flake setup), and then use nom build -f . [system name]

let
  pins = import ./npins;
  eval = import "${pins.colmena}/src/nix/hive/eval.nix" { rawHive = import ./hive.nix; };
in
eval.toplevel

you can at least work around 4 a little bit by having colmena set up the eval and then using nom directly, though you then have to colmena apply afterwards (which evals again). we just have a default.nix with (below, for a non-flake setup), and then use nom build -f . [optional system names]

let
  pins = import ./npins;
  eval = import "${pins.colmena}/src/nix/hive/eval.nix" { rawHive = import ./hive.nix; };
in
eval.toplevel

  nixpkgs.overlays = [
    (_: prev: {
      makeModulesClosure = x: prev.makeModulesClosure (x // { allowMissing = true; });
      pythonPackagesExtensions = prev.pythonPackagesExtensions ++ [
        (_: prev: builtins.listToAttrs (map (name:
          { name = name;
            value = prev.${name}.overridePythonAttrs (_: { doCheck = false; });
          }
        ) [ "dbus-next" "python-can" "curl-cffi" ])
    )];
    })
  ];

In reply to @quadradical:federated.nexus
i didnt even know you can type in spaces