From 1e4a5aa09c1c8f43722c9c260f011398799a8e8f Mon Sep 17 00:00:00 2001
From: Franck Cuny <franck@fcuny.net>
Date: Wed, 6 Mar 2024 06:29:24 -0800
Subject: rename `tools` to `packages` to follow convention

The convention is to use `pkgs` or `packages` for overlays and
definition of custom packages. Since I'm already using `pkg` for go,
I prefer to use `packages` for my scripts.
---
 packages/default.nix | 10 ++++++++++
 1 file changed, 10 insertions(+)
 create mode 100644 packages/default.nix

(limited to 'packages/default.nix')

diff --git a/packages/default.nix b/packages/default.nix
new file mode 100644
index 0000000..8e537c9
--- /dev/null
+++ b/packages/default.nix
@@ -0,0 +1,10 @@
+{ pkgs, ... }:
+
+pkgs.lib.makeScope pkgs.newScope (pkgs: {
+  # dnsmasq-to-html = pkgs.callPackage ./dnsmasq-leases-html { };
+  # git-blame-stats = pkgs.callPackage ./git-blame-stats { };
+  # git-broom = pkgs.callPackage ./git-broom { };
+  # ipconverter = pkgs.callPackage ./ipconverter { };
+  # perf-flamegraph-pid = pkgs.callPackage ./perf-flamegraph-pid { };
+  seqstat = pkgs.callPackage ./seqstat { };
+})
-- 
cgit v1.2.3