From: Patrick McLean <chutzpah@gentoo.org>
To: Brian Dolbec <dolsen@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Repoman rewrite stage3. Migrate check data to the tree
Date: Thu, 10 Mar 2016 18:40:31 -0800 [thread overview]
Message-ID: <20160310184031.4c9dd658@gentoo.org> (raw)
In-Reply-To: <20160310183007.027bb5f1.dolsen@gentoo.org>
On Thu, 10 Mar 2016 18:30:07 -0800
Brian Dolbec <dolsen@gentoo.org> wrote:
> So, where do we place this directory and what rules do we
> establish about it's modifications?
>
> location? : in the metadata dir alongside the install-qa-check.d
> directory?
That sounds reasonable to me, it is certainly metadata.
>
> name of the directory? : repoman, qa-rules, qa-data,
> repo-qa-data, ... ideas?
Something not project name specific, so nothing about repoman. Perhaps
something like "repo-checks", my personal vote would be make it a
directory with the contents being merged (so repo-checks.d maybe?)
>
> data format? : json (my favorite)
> compatible with many lanquages/interfaces
> is flexible to match various data types
> ie: dictionaries, lists, strings...
> is human readable/editable
> can be validated
>
> xml (PLEASE NO!)
>
> native python file (too language dependant)
>
> ini style (python configparser compatible) meh :/
>
> other ideas?
YAML - like JSON but made to be edited/read by humans (comment support
is a big feature). Also valid JSON is valid YAML. Also can be validated
just like JSON can.
next prev parent reply other threads:[~2016-03-11 2:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 2:30 [gentoo-dev] Repoman rewrite stage3. Migrate check data to the tree Brian Dolbec
2016-03-11 2:40 ` Patrick McLean [this message]
2016-03-11 18:35 ` Brian Dolbec
2016-03-12 18:01 ` Kristian Fiskerstrand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160310184031.4c9dd658@gentoo.org \
--to=chutzpah@gentoo.org \
--cc=dolsen@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox