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

This page summarizes the projects mentioned and recommended in the original post on reddit.com/r/NixOS
#Nix #Nixpkgs #TOML #Nixos #Direnv

Our great sponsors
  • SonarLint - Clean code begins in your IDE with SonarLint
  • Scout APM - Less time debugging, more time building
  • SaaSHub - Software Alternatives and Reviews
Our great sponsors

  • flk

    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

    Nix Packages collection

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

  • SonarLint

    Clean code begins in your IDE with SonarLint. Up your coding game and discover issues early. SonarLint is a free plugin that helps you find & fix bugs and security issues from the moment you start writing code. Install from your favorite IDE marketplace today.

  • flake-template

    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

    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'

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts