From c52c7f49f62b0baf6eb363b93ef2070ed8069397 Mon Sep 17 00:00:00 2001
From: Gabriel Arazas <foodogsquared@foodogsquared.one>
Date: Wed, 4 Sep 2024 14:28:53 +0800
Subject: [PATCH] wrapper-manager/sandboxing: update modules

---
 modules/wrapper-manager/sandboxing/boxxy.nix               | 2 +-
 modules/wrapper-manager/sandboxing/bubblewrap/launcher.nix | 5 +++++
 2 files changed, 6 insertions(+), 1 deletion(-)

diff --git a/modules/wrapper-manager/sandboxing/boxxy.nix b/modules/wrapper-manager/sandboxing/boxxy.nix
index 0390b150..337ae69a 100644
--- a/modules/wrapper-manager/sandboxing/boxxy.nix
+++ b/modules/wrapper-manager/sandboxing/boxxy.nix
@@ -107,7 +107,7 @@ in
                   "--rule ${ruleArg}")
                 submoduleCfg.rules);
 
-            arg0 = lib.getExe submoduleCfg.package;
+            arg0 = lib.getExe' submoduleCfg.package "boxxy";
             prependArgs = lib.mkBefore
               (submoduleCfg.extraArgs
                 ++ [ "--" config.sandboxing.wraparound.arg0 ]
diff --git a/modules/wrapper-manager/sandboxing/bubblewrap/launcher.nix b/modules/wrapper-manager/sandboxing/bubblewrap/launcher.nix
index 7345d3c7..cd1270c9 100644
--- a/modules/wrapper-manager/sandboxing/bubblewrap/launcher.nix
+++ b/modules/wrapper-manager/sandboxing/bubblewrap/launcher.nix
@@ -1,3 +1,8 @@
+# Module revolving around the specialized launcher. It is managed as a separate
+# project in the launcher subdirectory. Just look into the source code as you
+# would spelunk any other project. So far, the subproject itself doesn't have a
+# good state of testing (which is just used as a program for this very purpose)
+# so just use wrapper-manager's testing infra instead.
 { config, lib, options, pkgs, ... }:
 
 let