You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #5355, @Smona, @vigress8, @rycee, @exzombie and a few others collaborated to add the nixGL modules. This is great as it simplifies my configuration. Thank you very much.
Nevertheless, the support for Chromium seems problematic.
Looks like this would happen because the commandLineArgs are added in the buildCommand of chromium, which is overridden by the nixGL wrapper. We may need to try and extend the buildCommand instead of replacing it to fix this in all cases, but we'll have to see if that triggers a bunch of long package builds. Hopefully we won't have to implement a special case for wrapper packages like this one.
I wonder if we could override override on the wrapper derivation returned by nixGL.wrap, so that it basically maps (nixGL.wrap pkg).override { args } to (nixGL.wrap (pkg.override { args })).
Smona
linked a pull request
Nov 2, 2024
that will
close
this issue
Are you following the right branch?
Is there an existing issue for this?
Issue description
In #5355, @Smona, @vigress8, @rycee, @exzombie and a few others collaborated to add the nixGL modules. This is great as it simplifies my configuration. Thank you very much.
Nevertheless, the support for Chromium seems problematic.
Here is an example configuration:
This generates a
chromium
executable script which doesn't contain mycommandLineArgs
anymore.Workaround: remove
config.lib.nixGL.wrap
fromprograms.chromium.package
to get the command line arguments back.Maintainer CC
@Smona
System information
The text was updated successfully, but these errors were encountered: