[Mesa-dev] Move adriconf to mesa repositories
Emil Velikov
emil.l.velikov at gmail.com
Mon Apr 8 10:20:19 UTC 2019
On Thu, 4 Apr 2019 at 17:25, Jean Hertel <jean.hertel at hotmail.com> wrote:
>
> From: Emil Velikov <emil.l.velikov at gmail.com>
> Sent: 4th april, 2019 13:08
> >Yes I have interest in a configuration tool, although my vision varies
> >a lot from what adriconf and its predecessor.
>
> I'm super interested and open to hear yours, and other mesa devs, ideas
> on how a good configuration utility should look and behave.
> Feel free to reach over with ideas/suggestions/visions.
> Anything you think could make the current situation better.
>
> >That said, I don't mind if the project migrates under
> >gitlab.fd.o/mesa/ - it would be beneficial to have it close-by.
> >
> >What I would strongly suggest is to add some documentation about patch
> >submission, review process and releasing criteria/process.
>
> I will try to come up with something this weekend regarding
> patch submission, reviews and release criteria.
> As soon as I have some documentation I will come back to you.
>
> Thanks for the feedback on this.
>
Could not find my original notes, but the idea is roughly as follows:
- introduce a separate (user only?) library - say libmesa-config.so
- ^^ provides an API to query/set attributes, via numerical tokens
- any localisation is built on top of ^^ as standalone files
Reasoning:
- library reused by anyone to make a pretty config tool in their
toolkit and/or language
- numerical tokens are trivial to handle and cheap - can be
binned/deprecated easily
- translation lives outside of the driver - the driver doesn't care
about it, so don't bloat
- translators do not need access to mesa - one less hurdle/obstacle
Hope it makes sense, not sure if coffee has kicked in fully ;-)
-Emil
More information about the mesa-dev
mailing list