All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ross Burton <Ross.Burton@arm.com>
To: "JPEWhacker@gmail.com" <JPEWhacker@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][RFC] Layer Setup JSON schema and example
Date: Thu, 7 Jul 2022 10:02:59 +0000	[thread overview]
Message-ID: <CAA2FC7D-8003-431C-B856-B8DE9DCDC202@arm.com> (raw)
In-Reply-To: <20220706195311.974830-1-JPEWhacker@gmail.com>



> On 6 Jul 2022, at 20:53, Joshua Watt via lists.openembedded.org <JPEWhacker=gmail.com@lists.openembedded.org> wrote:
>
> Defines a common schema for layer setup that can be consumed by tools to
> know how to fetch and assemble layers for end users. Also includes an
> example of the layer setup that constructs poky for reference.

JSON is terrible for humans to read or edit, is this intended to be purely for the machine, or are humans meant to read it too?  If humans are meant to work on the file I’d really prefer something readable like YAML.

Ross
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

  parent reply	other threads:[~2022-07-07 10:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-06 19:53 [OE-core][RFC] Layer Setup JSON schema and example Joshua Watt
2022-07-06 21:10 ` Alexander Kanavin
2022-07-06 21:44   ` Joshua Watt
2022-07-07 10:02 ` Ross Burton [this message]
2022-07-07 10:17   ` Alexander Kanavin
2022-07-07 10:36     ` Ross Burton
2022-07-07 10:39       ` Alexander Kanavin
2022-07-07 13:14         ` Joshua Watt

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=CAA2FC7D-8003-431C-B856-B8DE9DCDC202@arm.com \
    --to=ross.burton@arm.com \
    --cc=JPEWhacker@gmail.com \
    --cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.