You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I find name+require_root perfect in "tool provides a system Daemon, and a ready-made plist to be put into /Library/LaunchDaemons" scenario. Like this service do:
service do
name macos: "cc.chlc.batt"
require_root true
end
It makes brew output the right command to run in the Caveats section, without the "or if you want to run it once, run [the run command]" latter half.
==> Caveats
To start batt now and restart at startup:
sudo brew services start [formula]
Therefore I think the audit rules should allow require_root to exist with name and without run.
brew audit currently complains that run must be defined to use methods other than name like [:require_root]. If I removed the require_root line, I'd have to ask users to ignore the subsequent non-sudo brew services start in Caveats. How weird would that sound!
The text was updated successfully, but these errors were encountered:
I find name+require_root perfect in "tool provides a system Daemon, and a ready-made plist to be put into /Library/LaunchDaemons" scenario. Like this service do:
It makes brew output the right command to run in the Caveats section, without the "or if you want to run it once, run [the run command]" latter half.
Therefore I think the audit rules should allow
require_root
to exist with name and withoutrun
.brew audit
currently complains thatrun
must be defined to use methods other thanname
like [:require_root]. If I removed the require_root line, I'd have to ask users to ignore the subsequent non-sudobrew services start
in Caveats. How weird would that sound!The text was updated successfully, but these errors were encountered: