2016-04-12 19:27 GMT+02:00 Ian Romanick <[email protected]>: > On 04/12/2016 09:39 AM, Marek Olšák wrote: >> On Tue, Apr 12, 2016 at 6:32 PM, Ian Romanick <[email protected]> wrote: >>> On 04/12/2016 05:21 AM, Marek Olšák wrote: >>>> On Mon, Apr 11, 2016 at 9:33 PM, Ian Romanick <[email protected]> wrote: >>>>> radeon and r200 have a driconf option that is similar to this. It sets >>>>> a default initial max anisotropy value. Maybe that would be better? >>>> >>>> If driconf didn't copy /etc/drirc into ~/.drirc, it would indeed be >>>> better. This needs to be fixed in driconf before we can consider it >>>> usable. After that, we can move such options there. >>> >>> I'm not sure what that means. You mean the driconf app? >> >> Yes, the driconf app. It unconditionally copies all app workarounds >> into ~/.drirc and following Mesa updates can't remove them. If you >> don't run driconf, ~/.drirc won't be created and you'll always get >> updated app workarounds with newer Mesa. > > That sounds awful... as a user, I'm pretty sure that would fill me with > rage. It seems like the app should only operate on the user's ~/.drirc. > Having an "import from /etc/drirc" button seems like the right answer. > Forcing it on people is never right. :(
Isn't the best strategy to overlay (merge) /etc/drirc with the users changes? Regards //Ernst _______________________________________________ mesa-dev mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/mesa-dev
