<ProofTechnique>
Are there any hacky ways to fake mtime on a home-manager managed file? Or, perhaps, a way to programmatically create a symlink to the actual file? My Emacs config is an org file, and I've currently got a line like `".emacs.d/config.org".source = ../emacs/config.org;`. `org-load-file` examines the mtime to determine if it needs to retangle the file before loading, but obviously Nix sets the mtime to 0
<ProofTechnique>
I _could_ just make a symlink in my rebuild wrapper, but that feels like cheating, and I'm hopeful maybe someone else has figured out something
<ProofTechnique>
Interesting! Let me try that out. Thanks!
<rycee>
ProofTechnique: Otherwise I imagine the most "Nixy" way would be to make a package that tangles the file at profile build time and symlinks the ready .el.
<ProofTechnique>
Yeah, that's the road I was gonna head down next :D
o1lo01ol1o has joined #home-manager
o1lo01ol1o has quit [Ping timeout: 256 seconds]
superherointj has joined #home-manager
<ProofTechnique>
I think I've settled on an activation script to just symlink directly to the config, for the moment. That seems to satisfy `org-babel-load-file`, at least. Might try to tackle the "tangle an org file and serve up the el" for the emacs-overlay, though :)
superherointj_ has joined #home-manager
superherointj_ has quit [Read error: Connection reset by peer]
superherointj_ has joined #home-manager
superherointj_ has quit [Read error: Connection reset by peer]
superherointj_ has joined #home-manager
superherointj_ has quit [Client Quit]
superherointj has quit [Quit: Leaving]
o1lo01ol1o has joined #home-manager
o1lo01ol1o has quit [Ping timeout: 246 seconds]
joesventek has quit [Quit: Quit]
joesventek has joined #home-manager
o1lo01ol1o has joined #home-manager
o1lo01ol1o has quit [Ping timeout: 256 seconds]
o1lo01ol1o has joined #home-manager
o1lo01ol1o has quit [Ping timeout: 256 seconds]
aforemny has quit [Ping timeout: 256 seconds]
aforemny has joined #home-manager
genevino has quit [Remote host closed the connection]
o1lo01ol1o has quit [Remote host closed the connection]
o1lo01ol1o has joined #home-manager
o1lo01ol1o has quit [Remote host closed the connection]
MmeQuignon has joined #home-manager
__monty__ has joined #home-manager
o1lo01ol1o has joined #home-manager
o1lo01ol1o has quit [Ping timeout: 272 seconds]
chvp has joined #home-manager
neiluj has joined #home-manager
<neiluj>
hello! got an issue with home manager (with flakes):
<neiluj>
all i did was to import home manager at the beginning of the main configuration file and then define a user
<neiluj>
the error: The option `home-manager.users' in `<unknown-file>' is already declared in ...
<chvp>
you should have two paths there
<chvp>
one in the ...
<chvp>
and one where the error occurs
<chvp>
that should help with trying to figure out why it thinks the option is declared twice
gchristensen has joined #home-manager
<neiluj>
chvp: indeed, i imported home-manager twice
<neiluj>
thanks!
cole-h has joined #home-manager
ardumont has quit [Ping timeout: 272 seconds]
o1lo01ol1o has joined #home-manager
o1lo01ol1o has quit [Ping timeout: 256 seconds]
ardumont has joined #home-manager
o1lo01ol1o has joined #home-manager
cole-h has quit [Remote host closed the connection]
aforemny has quit [Ping timeout: 256 seconds]
aforemny has joined #home-manager
rajivr has quit [Quit: Connection closed for inactivity]
o1lo01ol1o has quit [Remote host closed the connection]
eyJhb has joined #home-manager
<eyJhb>
__monty__: Might be correct
<eyJhb>
But I am not sure if anyone has tested the FF extensions/prefs thing in NIxpkgs.
<eyJhb>
TL;DR. currently testing the merged PR that added extensions+prefs+policies with a wrapper to Nixpkgs. Currently I can't get it to work... Doesn't really seem tested.
<eyJhb>
Would be cool to get to work, so we could have a uniform way of doing FF extensions, however, it would be outside of ~/.mozilla/firefox,
<__monty__>
Can you give a synopsis of the h-m module, the nixpkgs wrapper and your own method?
o1lo01ol1o has joined #home-manager
<eyJhb>
As far as I remember, the h-m module will create and mimic the infrastructure of ~/.mozilla/firefox, where extensions part of it is kinda hacky and not a "really supported method" but it works, for now (but I have heard there are some issues with that __monty__ ). The nixpkgs one that has been merged allows you to create a firefox wrapper, which utilises that firefox will look for settings
<eyJhb>
files relative to the bin file, which allows to specifiy policies.json, which allows to install extensions in a official way, which works quite well (the policies.json way, the actual implementation does not work as far as I can tell.), but would require one to have a firefox bin for each "profile" you want
<eyJhb>
My own way was to patch firefox (which required a rebulid of FF), to allow to load a policies.json on a pr, profile basis. So that used the best from h-m of emulating the ~/.mozilla/firefox, but having the policies.json in the profile which can control the extensions in a good way and oficially supported way. (and not require a bin for each profile you want)
o1lo01ol1o has quit [Ping timeout: 265 seconds]
<eyJhb>
And now nothing works with thi nixpkgs one...
o1lo01ol1o has joined #home-manager
o1lo01ol1o has quit [Ping timeout: 264 seconds]
justanotheruser has quit [Quit: WeeChat 2.9]
justanotheruser has joined #home-manager
o1lo01ol1o has joined #home-manager
pisquo has joined #home-manager
pisquo has quit [Client Quit]
cole-h has joined #home-manager
MmeQuignon has quit [Ping timeout: 246 seconds]
MmeQuignon has joined #home-manager
srk has quit [*.net *.split]
srk has joined #home-manager
MmeQuignon has quit [Ping timeout: 272 seconds]
__monty__ has quit [Quit: leaving]
justanotheruser has quit [Ping timeout: 246 seconds]