Summary: | sys-apps/portage: support a structured configuration file format (like toml or yaml) for miscellaneous settings | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Zac Medico <zmedico> |
Component: | Core - Configuration | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | gentoo |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 691798 |
Description
Zac Medico
2020-02-01 23:14:26 UTC
We'll need a a plugin framework, like the ebuild cache framework, so that people can choose practically any format. (In reply to Zac Medico from comment #1) > We'll need a a plugin framework, like the ebuild cache framework, so that > people can choose practically any format. The true test of that, however, is that you do have multiple implementations using that framework efficiently. Whilst we did see briefly a sqlite implementation (I believe, if I'm getting the right cache), I don't believe it's any better than the in-built? I'd like to see at least a template/reference implementation of one other format in addition to the 'preferred choice' so that contributors have a good starting point to use such a framework, otherwise it's a bit of a waste of time/effort providing for it. |