--nix-option should probably be passed down to the custom activation servers. #45

Open
opened 2026-03-15 23:43:03 +00:00 by janik · 0 comments

In Colmena you used to be able to specify e.g. max-jobs 0 and builders, which was quite useful if you wanted to e.g. preserve battery life on a laptop, and --build-on-target doesn't always work here because some machines aren't powerful enough, don't have enough space, etc... to eval and build their own closures.

Of course this is just some arbitrary example, there are many nix options that might be useful for arcana, and currently some of them are implemented as individual cli args (no_substitute, build_on_target, etc...), which seems futile, especially considering all the diverging nix implementations.

From what I can see most of the colmena specific cli args nix option mappings aren't handled by the custom activation code paths either, but that's a separate issue.

In Colmena you used to be able to specify e.g. `max-jobs` `0` and `builders`, which was quite useful if you wanted to e.g. preserve battery life on a laptop, and `--build-on-target` doesn't always work here because some machines aren't powerful enough, don't have enough space, etc... to eval and build their own closures. Of course this is just some arbitrary example, there are many nix options that might be useful for arcana, and currently some of them are implemented as individual cli args (`no_substitute`, `build_on_target`, etc...), which seems futile, especially considering all the diverging nix implementations. From what I can see most of the colmena specific cli args nix option mappings aren't handled by the custom activation code paths either, but that's a separate issue.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
arcana/arcana#45
No description provided.