All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: YP docs mailing list <docs@lists.yoctoproject.org>
Subject: what is the purpose of conf/distro/ dir with no distro definitions?
Date: Fri, 9 Apr 2021 06:53:51 -0400 (EDT)	[thread overview]
Message-ID: <4aedf060-309f-3e6e-c894-45b7481d56f2@crashcourse.ca> (raw)

[-- Attachment #1: Type: text/plain, Size: 873 bytes --]


  in current ref manual:

http://docs.yoctoproject.org/ref-manual/structure.html#meta-conf-distro

the definition of meta/conf/distro opens with:

  "The contents of this directory controls any distribution-specific
  configurations..."

fair enough, but what is the interpretation of a layer distro/
directory that does not define any actual distros? example:
meta-virtualization layer hierarchy contains:

  .
  ├── distro
  │   └── include
  │       ├── k8s-versions.inc
  │       ├── meta-virt-default-versions.inc
  │       ├── meta-virt-xen.inc
  │       └── virt_security_flags.inc
  └── layer.conf

so, sure, those .inc files can be useful, but that layer does not
contain any actual meta-virt-related <distro>.conf files, so are those
files really "distribution-specific configurations"?

  is there a better way to word that?

rday

                 reply	other threads:[~2021-04-09 10:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4aedf060-309f-3e6e-c894-45b7481d56f2@crashcourse.ca \
    --to=rpjday@crashcourse.ca \
    --cc=docs@lists.yoctoproject.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.