<jtojnar>
worldofpeace: I might be pushing it with breaking the gnome3 attrset, but hey
<worldofpeace>
jtojnar: you mean removing the `gnome3` attrset and moving everything to top-level?
<jtojnar>
that's my goal
<worldofpeace>
I think that's fine, the problem is that nix gives us no real way to group these things like other package managers in the wild
<jtojnar>
worldofpeace: do we need that?
<worldofpeace>
jtojnar: yes, and the only thing we have right now is the silly lists in gnome-3/default.nix
<worldofpeace>
lots of people have requests like "how do I install all the gnome3 sdk tools" (dconf-editor) and traditional managers give you a way to do this imperatively
<jtojnar>
well we have modules for that
<worldofpeace>
Yeah we could add options for that, enableGames etc.?
drakonis_ has joined #nixos-dev
<jtojnar>
I imagine gnome3 module will import gnome-core-packages, gnome-games-packages… profiles
<jtojnar>
and users will be able to create their lighter desktops by importing a subset of profiles
drakonis has joined #nixos-dev
<worldofpeace>
That's decent since we already have the concept of profiles. When you say gnome3 module imports these profiles is it guarded by an option, or do users that want to add one that's not default use `imports = [ <profile> ]`?
srk has joined #nixos-dev
drakonis_ has quit [Ping timeout: 276 seconds]
<jtojnar>
worldofpeace: I would think mostly importing non-default, but perhaps the default ones could be guarded to avoid the need to recreate everything
jtojnar has quit [Remote host closed the connection]
<worldofpeace>
So I guess we'll have services.xserver.desktopManager.gnome3.enable import the profiles that are default and probably whatever we think needs "tailoring". And the profiles are essentially package compilations that reflect gnome-build-meta jtojnar
jtojnar has joined #nixos-dev
drakonis1 has joined #nixos-dev
<ryantm>
marek++
<{^_^}>
marek's karma got increased to 6
drakonis1 has quit [Ping timeout: 250 seconds]
<jtojnar>
uugh, it's 6:20 AM here, time to hit the hay
<aanderse>
globin: no. tcp sockets in listen can still be achieved, but the use is not "encouraged" anymore. by using the rfc42'esque 'settings' option you can still have tcp connections.
<aanderse>
sure, there can be a use case for tcp sockets... but that is definitely an edge case, and not something that needs to be promoted given how dated the use of tcp in listen is
<aanderse>
so for example, you would simply write services.phpfpm.pools.mypool.settings.listen = "tcp blah"; instead of the current services.phpfpm.pools.mypool.listen = "tcp blah";
<aanderse>
note that using the current method will continue to work with the module as is, but now emit a warning that it deprecated and the user should update their configuration as the plan is to remove the ability to do that eventually
<gchristensen>
does this read properly? The multi-user installater on Linux will automatically configure proxy variables for the nix-daemon service. The installer will create a systemd override file at /etc/systemd/system/nix-daemon.service.d/override.conf with the value of each of the following environment variables: http_proxy, https_proxy, ftp_proxy, no_proxy, HTTP_PROXY, HTTPS_PROXY, FTP_PROXY, NO_PROXY.
<gchristensen>
s/installater/installer/
<gchristensen>
If any of these proxy-related variables are in the environment, then the installer will create an override file at /etc/systemd/system/nix-daemon.service.d/override.conf in order to pass it on to nix-daemon: http_proxy, https_proxy, ftp_proxy, no_proxy, HTTP_PROXY, HTTPS_PROXY, FTP_PROXY, NO_PROXY.
<samueldr>
(thinking like someone who reads it for the first time) what's the difference between http_proxy and HTTP_PROXY and what happens if both are set?
<gchristensen>
no clue
psyanticy has quit [Quit: Connection closed for inactivity]
orivej has joined #nixos-dev
pie_ has quit [Ping timeout: 268 seconds]
drakonis has joined #nixos-dev
pie_ has joined #nixos-dev
pie_ has quit [Remote host closed the connection]
pie_ has joined #nixos-dev
pie_ has quit [Ping timeout: 250 seconds]
pie_ has joined #nixos-dev
<jtojnar>
does anyone have a link to when eelco was writing about lazy module options or something like that?