<Mic92>
spacekookie: sphalerite niksnut I think we also need to announce our new steering committee member somewhere?
<niksnut>
guess so, don't remember what we did last time
<niksnut>
probably on the discourse topic
AlwaysLivid has quit [Read error: Connection reset by peer]
AlwaysLivid has joined #nixos-dev
<LnL>
sphalerite: I haven't really been keeping up with the rfc at all
kfound has quit [Remote host closed the connection]
jonringer has joined #nixos-dev
<sphalerite>
LnL: yet? ;)
abathur has joined #nixos-dev
FRidh has quit [Ping timeout: 256 seconds]
FRidh has joined #nixos-dev
kfound has joined #nixos-dev
Jackneill has quit [Ping timeout: 240 seconds]
Jackneill has joined #nixos-dev
orivej has joined #nixos-dev
justanotheruser has joined #nixos-dev
kfound has quit [Remote host closed the connection]
<domenkozar[m]>
a small company I know is looking for a Nix developer for 10h/week, mostly working on tasks that their developers don't know how to handle. It's 99% non-urgent tasks, sometimes it needs research sometimes hacks to be written. Lovely folks, whole team is remote and easy going. PM for details
<domenkozar[m]>
this is quite an ideal job if you're familiar with Nix and want to get the first gig :)
<domenkozar[m]>
if you don't know how to fix something it's fine
<eyJhb>
That sounds so nice ^, but it sounds like more advanced stuff?
<domenkozar[m]>
eh, it's not that advanced, just that their developers are quite new to Nix
<domenkozar[m]>
and they'd rather have the team focused on the product
<domenkozar[m]>
while someone that knows Nix can do those tasks
<eyJhb>
Oh if I had the time I would, it sounds like it would be a good opportunity to learn more Nix as well (granted, there would be some time spent "on your own")
<eyJhb>
I hope someone bites domenkozar[m] ! :)
<domenkozar[m]>
I think it's too good to be left hanging :)
<eyJhb>
Agreed
<eyJhb>
Especially the non-urgent stuff seems nice
saschagrunert has joined #nixos-dev
saschagrunert has quit [Ping timeout: 265 seconds]
ashkitten has quit [Ping timeout: 260 seconds]
ashkitten has joined #nixos-dev
mkaito has quit [Quit: WeeChat 2.9]
rajivr has quit [Quit: Connection closed for inactivity]
AlwaysLivid has quit [Ping timeout: 268 seconds]
AlwaysLivid has joined #nixos-dev
mkaito has joined #nixos-dev
mkaito has quit [Changing host]
mkaito has joined #nixos-dev
AlwaysLivid has quit [Ping timeout: 240 seconds]
AlwaysLivid has joined #nixos-dev
mkaito has quit [Quit: WeeChat 2.9]
mkaito has joined #nixos-dev
mkaito has joined #nixos-dev
mkaito has quit [Client Quit]
mkaito has joined #nixos-dev
orivej has quit [Ping timeout: 256 seconds]
cole-h has joined #nixos-dev
AlwaysLivid has quit [Ping timeout: 272 seconds]
FRidh has quit [Quit: Konversation terminated!]
evanjs has quit [Ping timeout: 264 seconds]
tdeo has quit [Read error: Connection reset by peer]
tdeo has joined #nixos-dev
halfbit has joined #nixos-dev
<halfbit>
when I set a crossSystem, I always seem to get a gcc debug wrapper like /nix/store/dc1ah88r1ychsz43kwpa283y82i4srqm-x86_64-unknown-linux-musl-stage-final-gcc-debug-wrapper-9.3.0
<halfbit>
is there a way to avoid the -debug variant?
<halfbit>
is this because strip is ignored in the gcc builder.sh in this case?
<halfbit>
what are the implications if stripping occurs for a cross compiler?
pmy_ has quit [Ping timeout: 265 seconds]
pmy_ has joined #nixos-dev
{^_^} has quit [Ping timeout: 260 seconds]
gchristensen has quit [Ping timeout: 260 seconds]
evanjs has joined #nixos-dev
terrorjack has quit [Quit: Ping timeout (120 seconds)]
terrorjack has joined #nixos-dev
<halfbit>
disabling that stripped check I think would save nearly 10-40MB on my closure in cases where I want to cross compile with gcc and musl to another arch
<halfbit>
since it removes musl-dev, bash, glibc deps