Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

copy evaluation store paths to iso #195

Closed
blaggacao opened this issue Mar 16, 2021 · 4 comments
Closed

copy evaluation store paths to iso #195

blaggacao opened this issue Mar 16, 2021 · 4 comments
Labels
enhancement New feature or request

Comments

@blaggacao
Copy link
Contributor

blaggacao commented Mar 16, 2021

If you, by-comer, are knowledgeable enough to solve #191 (comment), please do.

The goal is to also copy evaluations into the iso to avoid evaluation times on slow/low resource target machines.


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@blaggacao blaggacao added the enhancement New feature or request label Mar 16, 2021
blaggacao pushed a commit to blaggacao/devos that referenced this issue Mar 18, 2021
This is intended to cache avaluation and thereby cut evaulation
times within a live iso environment.

closes: divnix#195
Pacman99 pushed a commit to Pacman99/digga that referenced this issue Mar 18, 2021
This is intended to cache avaluation and thereby cut evaulation
times within a live iso environment.

closes: divnix#195
@Pacman99
Copy link
Member

I'm not sure if I misunderstand this. But no matter how many paths we add to the nix store by default, nix will still have to evaluate the nix expressions to figure out what store path it needs. And so if you're talking about evaluation caching, we would have to copy the evaluation cache sqlite databases which would result in an impure call to a file outside of the flake.

Perhaps we can lobby for a nix function that can evaluate an expression and output the evaluation cache.

@blaggacao
Copy link
Contributor Author

I think you are right. I'll test and report back. But probably you are right and my idea in Pacman99#2 is falling short of fixing this.

@Pacman99
Copy link
Member

I mean copying the drvPath is definitely an improvement. I assume it takes nix less time to get to the drv path than evaluate and get the store path.

@blaggacao
Copy link
Contributor Author

For lack of traction, for the te being I withdrawing from this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants