hraban
".: replacing existing signature" on activation
I use this in my configuration flake[^1] and when activating via darwin-rebuild I see the terminal output:
...
Activating setupLaunchAgents
Activating trampolineApps
.: replacing existing signature
.: replacing existing signature
.: replacing existing signature
.: replacing existing signature
.: replacing existing signature
.: replacing existing signature
.: replacing existing signature
.: replacing existing signature
.: replacing existing signature
.: replacing existing signature
.: replacing existing signature
.: replacing existing signature
.: replacing existing signature
.: replacing existing signature
.: replacing existing signature
adding /nix/store/62g9gzn37drwa6s617930w1jw03abxqq-slack-4.42.120/Applications/Slack.app
adding /nix/store/xhw4lf3gpmb9z3pffp2qnzcpg3vbv8hc-github-desktop-3.4.19/Applications/GitHub Desktop.app
It's not clear to me if .: is the result of some string or parsing issue. Looking at main.lisp I see that the multiple lines are a known issue, but it would be nice if the output varied to indicate which trampoline was being replaced, or something. This happens on both systems using nix-darwin.
[^1]: It's a bit of a mess but modules/darwin is where the macOS-specific configuration occurs.
The line you're indicating is printed by osacompile: https://github.com/hraban/mac-app-util/issues/3#issuecomment-2157138976
I'll add a comment in the repo because this is a recurring ticket on this repo and it becomes a red herring
Thanks for the reply, @hraban. What do you think about redirecting stdout and stderr (both of which seem to be required in my testing) from osacompile to suppress that diagnostic text?
I'm neutral on it. On the one hand I dislike messing with such a native tool in any way, on the other hand it's an eye sore and clearly a recurring point of confusion. I'm leaning towards it.
I do support the suppression of stdout and stderr, though if the module can expose an option to switch verbose mode, then it will be nice.
