veske has joined #nix-darwin
veske has quit [Ping timeout: 245 seconds]
disasm has joined #nix-darwin
eraserhd has joined #nix-darwin
<
eraserhd>
Is there a place where a derivation can just drop launch plists, like apps, where they'll get symlinked?
<
eraserhd>
Alternately, is there a way to point at a plist, say because it ships with a project?
<
LnL>
we generally mirror paths inside store paths
<
LnL>
so $out/Library/LaunchDaemons or $out/Library/LaunchAgents
<
LnL>
but there's nothing that links or activates these outside of ~/.nix-profile
<
eraserhd>
ok, so I can put these plists inside a derivation, but how do I specify to activate one?
<
eraserhd>
AFAICT, all the launchd configuration objects build new plists, and not activate existing ones.
<
eraserhd>
I guess environment.activationScripts?
<
LnL>
oh, you're using nix-darwin?
<
LnL>
not particularly nice, but I think adding it to the agents would work
<
LnL>
environment.launchDaemons."org.example.foo".source = "${pkgs.foo}/Library/LaunchDaemons/org.example.foo.plist";
matthewbauer has joined #nix-darwin
<
matthewbauer>
no access to my macbook right now
veske has joined #nix-darwin
veske has quit [Quit: This computer has gone to sleep]
<
LnL>
aha, pkgconfig
<
eraserhd>
LnL: Oh, that works.
* eraserhd
is thinking of porting NixOS's autossh service.
<
eraserhd>
buffer 40
<
LnL>
neat, if it makes sense for the package you could even add a module for it if you want
<
eraserhd>
What is the difference between a module and a service?
<
eraserhd>
I've not really understood some of the top-level layout of NixOS config.
<
LnL>
just an extra level of abstraction
<
LnL>
services.foo.enable = true; could configure the daemon for you
matthewbauer has quit [Ping timeout: 268 seconds]
matthewbauer has joined #nix-darwin
matthewbauer is now known as Guest54461
Guest54461 has quit [Killed (moon.freenode.net (Nickname regained by services))]
jtojnar has joined #nix-darwin
<
jtojnar>
LnL: do you think we need unwind support on Darwin?
<
LnL>
probably not, cc.find_library doesn't seem to work either so making auto_features conditional is probably best
<
jtojnar>
LnL: we do need auto_features, unless we want to enable all the codecs manually
<
LnL>
you can't disable it otherwise
<
jtojnar>
LnL: I would suggest disabling just the offending features
<
LnL>
auto_features=enabled overrules any other flags
<
jtojnar>
it should not IIRC
<
{^_^}>
mesonbuild/meson#5364 (by lazka, 6 weeks ago, open): feature option can't be set to auto when auto_features is set
<
jtojnar>
LnL: this is irrelevant
<
jtojnar>
auto_features sets what does .enabled() method returns for the options with type=feature & default=auto
<
jtojnar>
LnL: `-Dauto_features=enabled -Dunwind=disabled` should work as expected
<
LnL>
ah, maybe I only tried libunwind
<
jtojnar>
LnL: yeah, the other debugging libs will probably also need disabling
<
jtojnar>
LnL: sorry, the option should be `-Dlibunwind=disabled`
<
{^_^}>
#63637 (by LnL7, 39 seconds ago, open): gstreamer: re-enable auto_features
<
LnL>
must have re-enabled the comment with undo or something, making it seem like that c define worked
<
jtojnar>
LnL: looking at the legacy log, I do not see any mention of libunwind