<jaeger>
I'm thinking about the nvidia ports and the open vs. proprietary kernel modules. It seems like nvidia wants the open modules to be used going forward but I'd kinda like to allow either to be installed (not at the same time, they can't coexist) if for some reason the open ones don't work for a user. I was thinking about having the Pkgfile check an environment variable for it and including that in the
<jaeger>
README. Any thoughts/concerns?
<beerman>
I thought about that option a lot in the past, and always put it aside because i thought it was not KISS enough.. but I think it might be a good solution. It could be helpful in other cases (e.g. disabling xorg)
<jaeger>
In this case I think it's still simple enough because the default behavior requires no change on the user's part, at least
<jaeger>
open modules default, proprietary modules if NV_PROPRIETARY=1 or something like that
<beerman>
how do you plan to play that out? have a port that will pull in either that or the other dependency?
<jaeger>
The proprietary modules are included in the nvidia driver download file, the open ones come from a github repo
<jaeger>
So both can be pulled into one build
<beerman>
I see
<jaeger>
I thought about separating them into separate ports but now I'm leaning towards this way
<beerman>
to me, it sounds solid
<beerman>
yeah, one Pkgfile should do it, I agree
<cruxbridge>
<pitillo (@pitillo:crux.nu)> That sounds interesting, probably informing on the mailing list about this change could be great too
<braewoods>
It's a shame ports have no way to configure packages like gentoo does.
<braewoods>
I was just thinking this could be solved by something like that.
<braewoods>
perhaps you could have an environment file that gets sourced by pkgmk that expands to something: "${port name}_${variable}" and allow that to be user-settable.
<braewoods>
the Pkgfile sets the default value if the user has not already provided something.
<braewoods>
Only really makes a practical difference for stuff the user will basically always build.
<braewoods>
So little use for 'core'.
<braewoods>
so, yea, maybe you could add some kind of port specific environment variable system to allow for some limited changes to ports without having to edit it.