<infinisil>
I was just complaining about it in #52940 when I noticed it's somewhat of a standard approach to doing things (and meanwhile done by a couple more packages)
<samueldr>
hmm, any way it could be done with one unique wrapper, e.g. $(nix-share autojump) so it won't pollute PATH so much? I, too, dislike how it adds stuff in PATH
<samueldr>
and thinking about it, there's no way that one unique wrapper can do it and work as well as putting things in PATH :/
<infinisil>
samueldr: Ah yeah I thought of this too
<infinisil>
Something that buildEnv can do for all its inputs
Lingjian has joined #nixos-dev
<FRidh>
if you install in your profile the wrapper can look in each profile in NIX_PROFILES at share/*/, not?
<samueldr>
yeah
<samueldr>
though the more I think about it, the fewer cases I see where I cannot get the full path to its share location, without it being availble in profiles or already known
<samueldr>
e.g. you want to integrate fzf within a nix derivation? ${fzf}/share/fzf e.g. you nix-store --realise it? well you have the path already
<FRidh>
I do think we should aim at derivations declaring they provide this kind of data
<samueldr>
though one issue with a global thing is how do multiple derivations adding to that `fzf` folder act?
eadwu has quit [Ping timeout: 252 seconds]
<samueldr>
here we have the one canonical script *for fzf* knowing about it
<samueldr>
where the current method works, even though it isn't optimal
<infinisil>
"> how do multiple derivations adding to that `fzf` folder act"
<infinisil>
I think it's convention that all derivations use /share/${name} for their files (more or less)
<infinisil>
In my comment above I proposed something like /share/bash/sourceables/${name}
<samueldr>
some /usr/share folders are used as a melting pot where anything can add hooks or plugins or such things
<FRidh>
it's a step in the right direction
Lingjian has quit [Ping timeout: 250 seconds]
<samueldr>
are things `share` linked by default into profiles?
<domenkozar>
clever: are you running nixos on rbpi3?
<samueldr>
or is `pathsToLink` strictly a nixos thing?
<samueldr>
domenkozar: I have a rpi3b sitting next to me, running nixos, if it isn't clever-specific
<FRidh>
it's buildEnv
<domenkozar>
samueldr: I'm trying to get kodi to work
<domenkozar>
but it seems firmware doesn't work on 64bit
<domenkozar>
:((
<samueldr>
firmware?
orivej has joined #nixos-dev
<samueldr>
maybe try `linuxPackages_rpi` for the kernel, it's recently (a couple months back) been updated to work on aarch64
<infinisil>
samueldr: I thought /share is linked automatically, but now I'm not sure anymore, maybe it's only certain subdirectories of it
<samueldr>
infinisil: I'm not sure, which is why I'm asking, pathsToLink may be a different beast than for profiles
Lingjian has joined #nixos-dev
<FRidh>
for nixos there is also environment.pathsToLink and environment.extraOutputsToInstall and, I think more appliceable here, environment.shellInit . They could simply source it here
<domenkozar>
samueldr: raspberrypifw
<domenkozar>
it ships blobs for video hw acceleration
<samueldr>
hm, should it work on the mainline kernel?
Lingjian has quit [Read error: Connection reset by peer]
Lingjian has joined #nixos-dev
Lingjian has quit [Read error: Connection reset by peer]
Lingjian has joined #nixos-dev
<dtz>
infinisil: yessir
<dtz>
sorry for delay :)
<infinisil>
When I said "(build still failing with same error)" earlier, I messed up something with git and didn't use the latest commit at that point
sir_guy_carleton has quit [Quit: WeeChat 2.2]
<infinisil>
But I tried again as you can see from the comment and it does indeed build (libaom)
<dtz>
okay \o/
<dtz>
but still doesn't fix ffmpeg_4 it looks like QQ
<infinisil>
Oh, I haven't tested ffmpeg_4
<infinisil>
On linux everything works?
<dtz>
i mean, it seems to! :)
<dtz>
been using for a while, no problems :)
<infinisil>
Alright, hmm..
<dtz>
maybe just upstream ffmpeg build bug re:darwin? dunno
<infinisil>
Wait, the error mentions AVFoundation *checks if AVFoundation is somehow included in the build*
<infinisil>
Sure is
<infinisil>
I don't think that's it, but just to mention it: I'm running an outdated nix version on my mac
<infinisil>
Duh, it's the same error as ofborg
<infinisil>
Man I'm a bit slow today
<infinisil>
I'm also suspecting upstream bug now
orivej has joined #nixos-dev
Lingjian has quit [Ping timeout: 252 seconds]
Lingjian has joined #nixos-dev
<clever>
domenkozar: the last time i had full nixos running on an rpi, it was an armv6 build, on a rpi2 i think
<clever>
ive been having trouble getting them to netboot lately, and my sd cards are failing
nDuff has quit [Quit: zzz]
Lingjian has quit [Ping timeout: 252 seconds]
FRidh has quit [Remote host closed the connection]
eadwu has joined #nixos-dev
eadwu has quit [Ping timeout: 250 seconds]
eadwu has joined #nixos-dev
eadwu has quit [Ping timeout: 250 seconds]
boredom101 has joined #nixos-dev
eadwu has joined #nixos-dev
eadwu has quit [Ping timeout: 252 seconds]
eadwu has joined #nixos-dev
eadwu has quit [Ping timeout: 252 seconds]
<samueldr>
hey, now that I know teams can be mentioned, I took the initiative to create a @NixOS/backports team so people that want to *do* backports can be pinged as a group
<gchristensen>
nice
<samueldr>
I would highly recommend release managers to be added from now on to that team (and they can remove themselves after their stay) but I won't do it for RMs prior to me