<{^_^}>
#53447 (by timokau, 34 minutes ago, open): neovim-qt: wrap in separate derivation
<timokau[m]>
Is it because of the wrapper?
<gchristensen>
waiting on the evaluation to look, timokau[m]
<timokau[m]>
The wrappped package with the metadata still changed though, that doesn't matter?
<gchristensen>
the attribute which changed is neovim-qt
<gchristensen>
and the neovim-qt attribute has no maintainers
<timokau[m]>
Oh that makes sense
<timokau[m]>
Thanks for having a look
<gchristensen>
I've looked at 3-4 PRs this morning and I've managed to poo-poo them all
<gchristensen>
maybe I should stop for the morning
orivej has quit [Ping timeout: 250 seconds]
orivej has joined #nixos-borg
<samueldr>
gchristensen: what's wrong with passthru = { inherit unwrapped; }? while I find the whole wrapper/unwrapped concept clumsy in nixpkgs, I think it's better in the end that the wrapper derivation in some way provides what was wrapped; any downside I'm missing?
<gchristensen>
I wasn't remarking specifically on passthru, sorry
<samueldr>
it wasn't about `unwrapped`, but the file?
<gchristensen>
about compiling with one neovim and then swapping it out with a differently compiled one only in PATH
<samueldr>
s/file/whole change/
<samueldr>
ah
<samueldr>
yeah, that smells of unintended consequences :)
<gchristensen>
I should have written more
<gchristensen>
I think I woke up a bit sour today :(
<timokau[m]>
Its the same neovim, the one at runtime just has an added wrapper that passes it configuration