>>>>> On Sun, 26 Mar 2017, Brian Dolbec wrote: > I would much prefer for any new files to be created in a format that > most languages have data input modules for and are easily read/edited > by humans. While this can be read and split easily in python code. It > is not future proof for additional data being added and/or removed.
> For the repoman stage3 rewrites. I am moving all configurable data > from the code into yaml based files in /metadata/repoman. These files > will be easily edited by all developers for updates to banned eclasses > and various other values not needing code changes. > So with a general file name of arches.desc Is there any other data > that we want to include in that file? Possibly migrated from other > file(s). In that case a dictionary format yaml file might be best. > My example below has additional info over what was proposed. > It is an example only to show the possible benefit of such a file type. Please don't. Any such sophisticated file formats don't play well with standard Unix tools like grep. Also the file will have have to be used by tools like app-emacs/ebuild-mode, and to my knowledge there exists no solid parser for yaml in elisp. A simple text file with one record per line has the advantage that it can be easily parsed in any language. Ulrich
pgpWk4vLxZcia.pgp
Description: PGP signature
