Use remote package derivation file with nix-shell --packages option

• flk

  2 492 0.0 Shell

  A LISP that runs wherever Bash is

Hi, yes, that's possible. nix-shell -p 'callPackage (fetchGit https://github.com/chr15m/flk) {}' would do what you want if the repo had a default.nix file.

• nixpkgs

  973 15,656 10.0 Nix

  Nix Packages collection & NixOS

  

! nix-shell -I nixpkgs=https://github.com/nixos/nixpkgs/archive/master.tar.gz

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• flake-template

  1 0 0.0 Nix

  My template for Nix flakes

{ nixpkgs ? import {} }: { flk = nixpkgs.callPackage nix/package.nix {}; } which lets the outside world treat it as (import (fetchGit "blablah") {}).flk. Alternatively, the more recent convention is to simply be a Nix Flake, although that's still in beta. The way I would do it is reflected in my template, (minus the devshell bits) but it's not authoritative. Feel free to do it the old fashioned way too.

• devshell

  14 1,095 7.9 Nix

  Per project developer environments

  

Here's an example with devShell as a remote repository: sh nix-shell -p '(import (fetchGit "https://github.com/numtide/devshell") {}).cli'

Suggest a related project