TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Towards a Content-Addressed Model for Nix

45 pointsby figomoreabout 4 years ago

4 comments

devitabout 4 years ago
Seems like they only should depend on the parts of dependency that actually get incorporated in the dependent.<p>For instance:<p>- Changes to C source files of a shared library should not require a rebuild of dependents (assuming you don&#x27;t LTO with shared library bitcode)<p>- Changes to an executable in a dependency that you run as a child process during usage but not at build time should not require a rebuild of dependents
评论 #27073932 未加载
评论 #27073739 未加载
senkoraabout 4 years ago
I assume some of the difficulty comes from irreproducible builds. There’s been a lot of progress on that in the past few years.
评论 #27073614 未加载
l0b0about 4 years ago
tl;dr: Nix will soon be deciding whether to rebuild packages based on the <i>dependency contents</i> rather than the build inputs, which should result in much fewer rebuilds.<p>This is excellent news, and hopefully the savings will end up being used to run more aggressive tests and builds of lower priority packages, to have fewer breakages.
评论 #27074959 未加载
searealistabout 4 years ago
Sounds like bazel.
评论 #27094092 未加载