<samueldr>
the mouse cursor is not visible in our view
<worldofpeace>
ah samueldr
<adisbladis>
Someone who isn't me needs to look into why the zoom derivation takes _forever_ to build
<samueldr>
the trick is to keep re-using the same build that's GC rooted :)
<samueldr>
pro-mode: use it on the laptop you're not really using for anything else anyway
<adisbladis>
samueldr: But I don't wanna stick zoom either in my user profile or my system :/
<adisbladis>
samueldr: Ahh, one of those spare laptops...
<adisbladis>
I don't have one of those
<samueldr>
it's not spare, it's more about the fact that I'm not working away from my home office :)
<flokli>
adisbladis: it's bash and assembling the library list for autopatchelfhook
<samueldr>
a good point could also be "what's a channel?"
<adisbladis>
flokli: Ahh.. The wonders of nonfree software -.-
<samueldr>
tangibly, it's not obvious to understand what it is
<LnL>
good point
<adisbladis>
flokli: Do you know why we're not manually patching it?
<flokli>
adisbladis: I assume because autoPatchelfHook is more convenient (except it's slow)
<flokli>
if an ELF has a NEEDED which isn't satisfied in the buildInputs, it'll fail building
<flokli>
and not be a runtime error
<samueldr>
samuel dhurr lol
<flokli>
let's do the autopatchelf discussion elsewhere - i have a lot of ideas about it, but a bit too much for here ;-)
<worldofpeace>
samueldr: lol
<worldofpeace>
sorry
<samueldr>
no worries
<zimbatm>
I was going to mention the programs.sqlite :)
<zimbatm>
which is used by command-not-found
<samueldr>
"dee harr" is fine, just samuel, too; those are my last name initials, in case it's not obvious to y'all
<samueldr>
zimbatm: an alternative for those not using the channels is the command-not-found in nix-inde
<samueldr>
nix-index*
<worldofpeace>
I've gone through many variations samueldr :D
<zimbatm>
indeed
<samueldr>
I've not been using channels since about forever
<zimbatm>
we could also talk about the channels: URI shortcut
<samueldr>
good point zimbatm
<worldofpeace>
yep zimbatm
<samueldr>
also how channels work on the system, tangibly
<samueldr>
how it maps to NIX_PATH
<zimbatm>
👍
<samueldr>
compared to using NIX_PATH=nixpkgs=$HOME/my-nixpkgs-checkout
<samueldr>
(I don't have a default NIX_PATH with .nix-defexpr and not exactly used to it)
<samueldr>
(btw I know the explanations, I just think that in this channels extravaganza they're helpful topics)
<adisbladis>
<3 samueldr
<{^_^}>
samueldr's karma got increased to 147
<adisbladis>
Totally not obvious or easily discoverable topics
<worldofpeace>
yep, this is actually a bit of confusion I first had when first using nixos
<worldofpeace>
and I was like Oh
<zimbatm>
also good to know, `nix-channel --list` doesn't respect the NIX_PATH and only lists the user channels, even if the user has the root channels on the NIX_PATH
<adisbladis>
Luckily I found out early, so I never really used channels
<samueldr>
ooh, don't forget about names that are not specifically listed
<zimbatm>
`nix-channel --list` vs `sudo nix-channel --list` can be confusing
<samueldr>
NIX_PATH=$PWD;
<samueldr>
<foobar> will look in $PWD/foobar
<adisbladis>
zimbatm: Not to speak of that it doesn't even list root channels...
<zimbatm>
where prefixModule is a special kind of wrapper
<zimbatm>
that maps all the config and options to a prefix for the module
<zimbatm>
and the mediawiki.nix module can only access config options for itself
<worldofpeace>
eyJhb: hibernation -> new year rebirth? tldr, I'm brand new
<zimbatm>
then you can start configuring the service `prefixes.mediawiki1.enable = true;`
<infinisil>
zimbatm: Sounds like just an option for e.g. `services.mediawiki.instance1 = ...`
<infinisil>
Which is already possible with `type = attrsOf (submodule ...)`
<zimbatm>
infinisil: the difference would be that the module is not loaded by default, and have a bit of a different interface
<zimbatm>
so you would have `nixpkgs/services` that contains those networked-services
<zimbatm>
the advantage is that writing more services wouldn't slow down the nixos evaluation because they are not loaded by default
<zimbatm>
and that they can have any number of instances by default as well
<zimbatm>
at the moment the module has to be designed specifically to support multiple instances
<gchristensen>
another nice advantage is being able to have multiple instances without much trouble
<gchristensen>
it is possible to do that now, but it is a bit ugly
<zimbatm>
we would impose restrictions on the service definition, it would be a subset of the systemd unit
<zimbatm>
like DynamicUser is always true
<gchristensen>
yeah
<gchristensen>
nice
<zimbatm>
on the nixos side, we would map those to systemd units
<gchristensen>
btw, if we get 8 more subscribers we can get a fancy pants Youtube channel URL :)
<zimbatm>
but then they would be re-usable by other systems as well
<zimbatm>
anyways, that's the dream that's a bit in the air
<aanderse>
<infinisil "So instead of options for nginx,"> yeah i think aszlig (sp?) worked on that for web services/applications and databases in the past
<gchristensen>
zimbatm: I like it a lot
<aanderse>
i'm not a functional programmer... but doing that does seem in the spirit of nixos
<aanderse>
of course the implementation... that is another thing
<gchristensen>
zimbatm: probably /many/ services don't need the full power of the module system
<aanderse>
maybe it doesn't work out so nice
<zimbatm>
gchristensen: yeah exactly
<gchristensen>
or could be in a "read only" mode, taking inputs explicitly with no write permission
<zimbatm>
maybe one day I will give it a try if nobody beats me to it
evils has joined #nixos-officehours
stolyaroleh has quit [Quit: Konversation terminated!]