rycee changed the topic of #home-manager to: Support and discussion around the Home Manager project (https://github.com/rycee/home-manager) | Logs: https://logs.nix.samueldr.com/home-manager
cole-h has quit [Quit: Goodbye]
evanjs has quit [Read error: Connection reset by peer]
evanjs has joined #home-manager
liff has quit [Ping timeout: 260 seconds]
liff has joined #home-manager
c0c0 has joined #home-manager
quinn has quit [Quit: ZNC 1.7.5 - https://znc.in]
asymptotically has joined #home-manager
hmpffff has joined #home-manager
hmpffff has quit [Quit: nchrrrr…]
hmpffff has joined #home-manager
__monty__ has joined #home-manager
<__monty__> So I added a firefox package in an overlay that simply fetches a dmg and extracts the app. To pass to `programs.firefox.package`. The package installed, which afaict HM did but I can't find a ~/.mozilla to check my profiles were installed correctly. (Ideally I don't have to start firefox to check because I assume it'll create the directory and just be a confounding factor.)
<__monty__> Should programs.firefox install profiles in ~/.mozilla? And if not where *does* it install them?
<__monty__> Alternatively will configured profiles not be installed at all unless the firefox package is the right wrapped/unwrapped package depending on stateVersion and if so, how do I make my overlayed package act like firefox wrapped/unwrapped?
hmpffff has quit [Quit: nchrrrr…]
c0c0 has quit [Ping timeout: 256 seconds]
c0c0 has joined #home-manager
hmpffff has joined #home-manager
hmpffff has quit [Client Quit]
hmpffff has joined #home-manager
c0c0 has quit [Ping timeout: 240 seconds]
c0c0 has joined #home-manager
johnw has joined #home-manager
c0c0 has quit [Ping timeout: 258 seconds]
MmeQuignon has joined #home-manager
hmpffff has quit [Quit: nchrrrr…]
cole-h has joined #home-manager
claudiii has quit [Ping timeout: 240 seconds]
claudiii has joined #home-manager
hmpffff has joined #home-manager
quinn has joined #home-manager
hmpffff has quit [Quit: nchrrrr…]
hmpffff has joined #home-manager
<kloenk> Did someone evaluate that home-manager is running under mipsel-linux? my checks for that system are failing, but the home-manager derivation states that it can run ther
hmpffff has quit [Quit: nchrrrr…]
<hexa-> Why would modules be arch dependant?
<hexa-> Usually the packages specify their platform
<NobbZ[m]> Probably because they relate to arch dependant software?
<hexa-> Sure, but those are in nixpkgs
<simpson> Sometimes architecture matters, even when it shouldn't matter. Computers are fun in that way.
<hexa-> Hah yeah
hmpffff has joined #home-manager
hmpffff has quit [Quit: nchrrrr…]
__monty__ has quit [Quit: leaving]
asymptotically has quit [Quit: Leaving]
hmpffff has joined #home-manager
<rycee> kloenk: Good idea :-) I added a basic issue template. I've also started looking at including a table of maintainers in the manual so it'll be easier to see who to ping.
<rycee> __monty__: Sorry, I don't know how well it would work with an external Firefox install. I can't think of any obvious issue why it wouldn't work. You'll still have the nix installed Firefox but if your homebrew version is first in PATH then it should be used instead.
<rycee> __monty__: And you can get addon ID and download URL from the guid field in Mozilla's REST API: `http 'https://addons.mozilla.org/api/v4/addons/addon/tridactyl-vim/?lang=en-US';`
<rycee> … for example.
hmpffff has quit [Quit: nchrrrr…]
<rycee> pistache: HM doesn't attempt to do anything directly with `/etc/set-environment`, it is sourced by `/etc/profile`.
<rycee> __monty__: The Firefox profiles go in `~/.mozilla/firefox/`, you should have a `profiles.ini` symlink in there if you have enabled Firefox profile management in HM.
<rycee> kloenk: I don't know about mipsel-linux but I know some use HM on Android but I guess most of those devices are ARM based.
<rycee> In principle modules can be disabled for some architectures and ideally a module should be disabled if the software managed by the module does not support the platform or OS you're on.
MmeQuignon has quit [Ping timeout: 272 seconds]