NixOS/nix
Ver no GitHubCollect "file system object" parts of `libnixutil` together
Open
#9.278 aberto em 2 de nov. de 2023
good first issueidea approved
Métricas do repositório
- Stars
- (9.803 stars)
- Métricas de merge de PR
- (Mesclagem média 4d 12h) (86 fundiu PRs em 30d)
Description
We now have bunch of involved code for working with file system objects.
Someday it might be good to codify this into a new libnixfile. (Don't worry, that doesn't mean I am planning a "file-only" Nix!) But going down that road would mean lots of little libraries, which could have implications for dynamic linking. For now we can instead group files into subdirectories (see build/ in libstore for this same concept), but keep all such directories linked together in the parent library.
For initial contents I am thinking:
src/libutil/archivesrc/libutil/canon-pathsrc/libutil/fs-sinksrc/libutil/git.ccwill contain more stuff after #8918src/libutil/posix-source-accessorsrc/libutil/source-accessorsrc/libutil/file-content-addressNew, doesn't distinguish between "flat" and "text" because w.r.t file system objects (as opposed to store objects) they are the same.
I think this will continue growing too based on our current plans. libnixfetchers only barely depends on the store layer anyways, so I think some or even all of it could end up here too.