[csw-devel] SF.net SVN: opencsw:[398] catalog_signatures/catalog_gpg

[Peter Bonivart]

2011/7/22 Maciej Bliziński <maciej at opencsw.org>:
> The main benefit is that you use a standard file format that gives you a
> data structure, e.g. a dictionary of lists.
>
> To use a simple text format, we need to design it well. For example, keeping
> multiple dictionaries of lists in one file might be annoying to parse in
> shell. On the other hand, you don't want to create one file per variable,
> because this can kill performance (start up times). Having a command line
> utility has the advantage that you can change the underlying mechanics
> without changing the API. If you use text files, it is harder to change that
> because you might have 15 different parsers already scattered throughout the
> code (and the world), with different bugs and quirks.
>
> Simple text files might still be better; I just wanted to point out that
> there are concrete benefits of using a standard file format.

Can you give an example of the data we will store in these files? So
far I've heard of architecture and releases and they wouldn't need
anything more fancy than something like this:

arch = i386 sparc
release = 5.9 5.10 5.11

/peter