All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randolph Sapp <rs@ti.com>
To: <denis@denix.org>, <reatmon@ti.com>, <afd@ti.com>, <c-shilwant@ti.com>
Cc: <meta-arago@lists.yoctoproject.org>
Subject: [meta-arago][master][discussion] Qt package groups and config locations
Date: Fri, 24 Jan 2025 15:54:35 -0600	[thread overview]
Message-ID: <D7AMZ4EPPP5M.2NTHC4Y4JP2H7@ti.com> (raw)

Hey,

Asking for some general advice before I submit the next series. Cleaning up
meta-qt* package groups and everything there is a bit of a logistical argument
to be made.

We now have an official requirement tracking Qt6 enablement which means more
automated testing. At the same time I do not think meta-arago should be
inherently dependent on a layer as heavy as meta-qt*. I'm planning on making a
series of isolated package groups and configs that can be toggled through a
distro feature.

Where do we think this should belong? The distro layer or the extras layer? I'm
leaning toward the distro layer as these are ultimately distro specific configs,
but I can understand that some may believe this is inherently "extra" content.
Regardless, the test layer will need to be updated to point to this.

Maybe it should be a generic "software" layer? I don't like splitting things
unnecessarily, but this is a weird example where we need certain features
enabled for both testing and release, but it doesn't really make sense to
duplicate it. No clue. Any opinions?

Regards,
Randolph


             reply	other threads:[~2025-01-24 21:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-24 21:54 Randolph Sapp [this message]
2025-01-24 23:14 ` [meta-arago][master][discussion] Qt package groups and config locations Ryan Eatmon
2025-01-25  0:10   ` Randolph Sapp

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=D7AMZ4EPPP5M.2NTHC4Y4JP2H7@ti.com \
    --to=rs@ti.com \
    --cc=afd@ti.com \
    --cc=c-shilwant@ti.com \
    --cc=denis@denix.org \
    --cc=meta-arago@lists.yoctoproject.org \
    --cc=reatmon@ti.com \
    /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.