nvfetcher: Generate nix sources expr for the latest version of packages

[ library, mit, nix, program ] [ Propose Tags ]

Please see README

[Skip to Readme]
Versions [RSS] [faq],,,
Change log CHANGELOG.md
Dependencies aeson (>=1.5.6 && <1.6), base (>=4.8 && <5), binary, binary-instances (>=1.0.1 && <1.1), bytestring, containers, data-default (>=0.7.1 && <0.8), extra (>=1.7.9 && <1.8), free (>=5.1.5 && <5.2), microlens, microlens-th, neat-interpolation (>=0.5.1 && <0.6), nvfetcher, optparse-simple (>=0.1.1 && <0.2), parsec, shake (>=0.19.4 && <0.20), text, tomland (>=1.3.2 && <1.4), transformers, unordered-containers, validation-selective [details]
License MIT
Copyright 2021 berberman
Author berberman
Maintainer berberman <berberman.yandex.com>
Category Nix
Home page https://github.com/berberman/nvfetcher
Bug tracker https://github.com/berberman/nvfetcher/issues
Source repo head: git clone https://github.com/berberman/nvfetcher.git
Uploaded by berberman at 2021-09-26T23:52:27Z
Distributions NixOS:
Executables example, nvfetcher
Downloads 228 total (20 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Hackage Matrix CI
Docs not available [build log]
All reported builds failed as of 2021-09-27 [all 2 reports]


  • NvFetcher
    • NvFetcher.Core
    • NvFetcher.ExtractSrc
    • NvFetcher.FetchRustGitDeps
    • NvFetcher.NixExpr
    • NvFetcher.NixFetcher
    • NvFetcher.Nvchecker
    • NvFetcher.Options
    • NvFetcher.PackageSet
    • NvFetcher.Types
      • NvFetcher.Types.Lens
      • NvFetcher.Types.ShakeExtras

Manual Flags


Build example executable

Automatic Flags

Use -f <flag> to enable a flag, or -f -<flag> to disable that flag. More info


Maintainer's Corner

For package maintainers and hackage trustees


Readme for nvfetcher-

[back to package description]


Hackage MIT license nix

nvfetcher is a tool to automate nix package updates. It's built on top of shake, integrating nvchecker. nvfetcher cli program accepts a TOML file as config, which defines a set of package sources to run.


For example, feeding the following configuration tonvfetcher:

# nvfetcher.toml
src.pypi = "feeluown"
fetch.pypi = "feeluown"

src.github = "IsoaSFlus/QLivePlayer"
fetch.github = "IsoaSFlus/QLivePlayer"
git.fetchSubmodules = true

it can create sources.nix like:

# sources.nix
{ fetchgit, fetchurl }:
  feeluown-core = {
    pname = "feeluown-core";
    version = "3.7.7";
    src = fetchurl {
      sha256 = "06d3j39ff9znqxkhp9ly81lcgajkhg30hyqxy2809yn23xixg3x2";
      url = "https://pypi.io/packages/source/f/feeluown/feeluown-3.7.7.tar.gz";
  qliveplayer = {
    pname = "qliveplayer";
    version = "3.22.1";
    src = fetchgit {
      url = "https://github.com/IsoaSFlus/QLivePlayer";
      rev = "3.22.1";
      fetchSubmodules = true;
      deepClone = false;
      leaveDotGit = false;
      sha256 = "00zqg28q5xrbgql0kclgkhd15fc02qzsrvi0qg8lg3qf8a53v263";

We tell nvfetcher how to get the latest version number of packages and how to fetch their sources given version numbers, and nvfetcher will help us keep their version and prefetched SHA256 sums up-to-date, stored in _sources/generated.nix. Shake will handle necessary rebuilds as long as you keep _sources directory -- we check versions of packages during each run, but only prefetch them when needed.

Live examples

How to use the generated sources file? Here are several examples:

  • DevOS - Packages are defined in TOML

  • My flakes repo - Packages are defined in eDSL

  • Nick Cao's flakes repo - Packages are defined in TOML


nvfetcher package is available in nixpkgs, so you can try it with:

$ nix-shell -p nvfetcher

This repo also has flakes support:

$ nix run github:berberman/nvfetcher

To use it as a Haskell library, the package is available on Hackage. If you want to use the Haskell library from flakes, there is also a shell ghcWithNvfetcher:

$ nix develop github:berberman/nvfetcher#ghcWithNvfetcher
$ runghc Main.hs

where you can define packages in Main.hs. See Haskell library for details.


Basically, there are two ways to use nvfetcher, where the difference is how we provide package sources definitions to it.


To run nvfetcher as a CLI program, you'll need to provide package sources defined in TOML.

Available options:
  --version                Show version
  --help                   Show this help text
  -o,--build-dir FILE      Directory that nvfetcher puts artifacts to
                           (default: "_sources")
  --commit-changes         `git commit` changes in this run (with shake db)
  -l,--changelog FILE      Dump version changes to a file
  -j NUM                   Number of threads (0: detected number of processors)
                           (default: 0)
  -r,--retry NUM           Times to retry of some rules (nvchecker, prefetch,
                           nix-instantiate, etc.) (default: 3)
  -t,--timing              Show build time
  -v,--verbose             Verbose mode
  TARGET                   Two targets are available: 1.build 2.clean
                           (default: "build")
  -c,--config FILE         Path to nvfetcher TOML config
                           (default: "nvfetcher.toml")

Each package corresponds to a TOML table, whose name is encoded as table key, with two required fields and three optional fields in each table. You can find an example of the configuration file, see nvfetcher_example.toml.


Version source -- how do we track upstream version updates?

  • src.github = owner/repo - the latest github release
  • src.github_tag = owner/repo - the max github tag, usually used with list options (see below)
  • src.pypi = pypi_name - the latest pypi release
  • src.git = git_url (and an optional src.branch = git_branch) - the latest commit of a repo
  • src.archpkg = archlinux_pkg_name -- the latest version of an archlinux package
  • src.aur = aur_pkg_name -- the latest version of an aur package
  • src.manual = v -- a fixed version, which never updates
  • src.repology = project:repo -- the latest version from repology
  • src.webpage = web_url and src.regex -- a string in webpage that matches with regex
  • src.httpheader = request_url and src.regex -- a string in http header that matches with regex
  • src.openvsx = publisher.ext_name -- the latest version of a vscode extension from open vsx
  • src.vsmarketplace = publisher.ext_name -- the latest version of a vscode extension from vscode marketplace

Optional list options for some version sources (src.github_tag, src.webpage, and src.httpheader), see the corresponding nvchecker documentation for details.

  • src.include_regex
  • src.exclude_regex
  • src.sort_version_key
  • src.ignored

Optional global options for all kinds of version sources, see the corresponding nvchecker documentation for details. You can tweak obtained version number using this option, e.g. stripping the prefix v or transforming the result by regex.

  • src.prefix
  • src.from_pattern
  • src.to_pattern

Nix fetcher

How do we fetch the package source if we have the target version number? $ver is available in string, which will be set to the result of nvchecker.

  • fetch.github = owner/repo
  • fetch.pypi = pypi_name
  • fetch.git = git_url
  • fetch.url = url
  • fetch.openvsx = publisher.ext_name
  • fetch.vsmarketplace = publisher.ext_name

Optional nix-prefetch-git config, which make sense only when the fetcher equals to fetch.github or fetch.git. They can exist simultanesouly.

  • git.deepClone
  • git.fetchSubmodules
  • git.leaveDotGit

Extract src

Optional extract src config, files are extracted into build directory, and then read by readFile in generated nix expr.

  • extract = [ "file_1", "file_2", ...] - file paths are relative to the source root

Rust support

rustPlatform.buildRustPackage now accepts an attribute cargoLock to vendor dependencies from Cargo.lock, so we can use this instead TOFU cargoSha256 for Rust packageing. nvfetcher supports automating this process, extracting the lock file to build and calculating cargoLock.outputHashes, as long as you set the config

  • cargo_lock = cargo_lock_path - relative to the source root


passthru config, an additional set of attrs to be generated.

  • passthru = { k1 = "v1", k2 = "v2", ... }

Haskell library

nvfetcher itsetlf is a Haskell library as well, whereas the CLI program is just a trivial wrapper of the library. You can create a Haskell program depending on it directly, by using the runNvFetcher entry point. In this case, we can define packages in Haskell language, getting rid of TOML constraints.

You can find an example of using nvfetcher in the library way, see Main_example.hs.


For details of the library, documentation of released versions is available on Hackage, and of master is on our github pages.


Issues and PRs are always welcome. _(:з」∠)_

Building from source:

$ git clone https://github.com/berberman/nvfetcher
$ nix develop
$ cabal build