![]() ![]() This split motivates some of the UI choices for Nix-style local buildĬommands. ![]() Will just rebuild everything it needs on its next invocation). Store is corrupted), deleting this directory is safe ( v2-build Whatever reason (e.g., to reclaim disk space or because the global Global store-dir option) if you need to clear your store for ![]() The global package store is ~/.cabal/store (configurable via Identify the result of a build if we compute this identifier and weįind that we already have this ID built, we can just use the already The inputs which would influence the compilation of a package (flags,ĭependency selection, etc.). These build products are identified by a hash that over all of When an external package does not depend on an inplace package, it canīe built and installed to a global store, which can be shared across The source code for external packages is usually An external package is any package which is not listed in the.Suitable for packages which you want to edit and recompile. Packages are not cached and not given unique hashes, which makes them Specifically for the project and are not installed globally. Them, are built inplace, meaning that they are always built Local packages, as well as the external packages (below) which depend on Usually, these refer to packages whose source code livesĭirectly in a folder in your project (although, you can list anĪrbitrary Hackage package in extra-packages to force it to be Packages, optional-packages or extra-packages field of a A local package is one that is listed explicitly in the.Must be built per-project, versus external packages, which can be cached One of the primary innovations of Nix-style local builds is theĭistinction between local packages, which users edit and recompile and ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |