| 30 Mar 2022 |
CRTified | Good question, but it recently started to hang at that point for me, too 🤔 Thought that it was caused by the (at that point) unstable network connection | 16:37:29 |
Zhaofeng Li | After it says "Starting..." it will invoke nix-copy-closure | 22:29:51 |
Zhaofeng Li | Maybe there are some environment variables that affect its logging | 22:30:16 |
| 2 Apr 2022 |
@github:maunium.net | [zhaofengli/colmena] zhaofengli closed
issue
#62: nix-eval-jobs patch causes build failure with nixos-21.11 nixpkgs
| 03:03:42 |
| 3 Apr 2022 |
@github:maunium.net | [zhaofengli/colmena] blaggacao opened
issue
#70: `meta.nixpkgs`
I think this interface is not necessary and using the equivalent upstream interfaces would lead to less confusion.
- In a flakes world, the way to determine
meta.nixpkgs would be as follows: inputs.colmena.inputs.nixpkgs.follows = "";
| 00:56:05 |
@github:maunium.net | [zhaofengli/colmena] blaggacao edited
issue
#70: `meta.nixpkgs`
| 00:56:31 |
@github:maunium.net | [zhaofengli/colmena] blaggacao edited
issue
#70: `meta.nixpkgs`
| 00:56:45 |
@github:maunium.net | [zhaofengli/colmena] blaggacao closed
issue
#69: Deploying home-manager profiles
| 00:57:37 |
@github:maunium.net | [zhaofengli/colmena] blaggacao opened
issue
#71: meta.nodeNixpkgs
It is really a nightmare in terms of composability to have this attribute exposed via meta. I wonder if it would be possible instead to expose it via the normal (composable) module system and shallow evaluate for peek. something like this:
let
colmenaNixpkgs = {
options.colmenaNixpkgs = {};
};
in (nixpkgs.lib.evalModules { modules = [colmenaNixpkgs]; check = false; }).colmenaNixpkgs
| 05:26:00 |
@github:maunium.net | [zhaofengli/colmena] blaggacao opened
issue
#72: Evaluation
I saw your efforts to speed up evaluation. This might be a project that you might keep an eye on: https://github.com/kamadorueda/santiago
Not immediately useful.
| 22:22:54 |
| 4 Apr 2022 |
@github:maunium.net | [zhaofengli/colmena] Repo forked into blaggacao/colmena | 00:07:31 |
@github:maunium.net | [zhaofengli/colmena] blaggacao opened
pull request
#73: imp: soc of eval, modules & options
-
the reason for this change is to have more transparent separation
of concern between effectuations of the module system and pre-module
system effectuations
-
with improved flakes support down the line, pre-module system
effectuations will get more complex
-
if the code was clean before, this does not introduce a change in
behaviour. Unclean prior code, could now be surfaced by this.
| 00:07:43 |
@github:maunium.net | Redacted or Malformed Event | 00:08:55 |
@github:maunium.net | Redacted or Malformed Event | 00:10:47 |
@github:maunium.net | Redacted or Malformed Event | 00:25:37 |
@github:maunium.net | Redacted or Malformed Event | 00:27:46 |
@github:maunium.net | Redacted or Malformed Event | 02:12:37 |
@github:maunium.net | Redacted or Malformed Event | 02:12:39 |
@github:maunium.net | Redacted or Malformed Event | 02:14:06 |
@github:maunium.net | Redacted or Malformed Event | 02:14:41 |