Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Denys Dmytriyenko" <denis@denix.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Anuj Mittal <anuj.mittal@intel.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 2/2] gstreamer1.0-plugins-good: add qt5 PACKAGECONFIG
Date: Tue, 24 Mar 2020 15:32:22 -0400	[thread overview]
Message-ID: <20200324193222.GA1578@denix.org> (raw)
In-Reply-To: <467110132be087c26851033a7b9e45972b5c0bd4.camel@linuxfoundation.org>

On Tue, Mar 24, 2020 at 07:29:42PM +0000, Richard Purdie wrote:
> On Tue, 2020-03-24 at 14:43 -0400, Denys Dmytriyenko wrote:
> > On Tue, Mar 24, 2020 at 02:33:19PM -0400, Denys Dmytriyenko wrote:
> > > On Tue, Mar 24, 2020 at 06:15:51PM +0000, Richard Purdie wrote:
> > > > On Tue, 2020-03-24 at 14:12 -0400, Denys Dmytriyenko wrote:
> > > > > On Tue, Mar 24, 2020 at 06:07:44PM +0000, Richard Purdie wrote:
> > > > > > On Tue, 2020-03-24 at 13:58 -0400, Denys Dmytriyenko wrote:
> > > > > > > On Fri, Feb 21, 2020 at 10:41:58AM +0800, Anuj Mittal
> > > > > > > wrote:
> > > > > > > > Instead of disabling unconditionally, add PACKAGECONFIG
> > > > > > > > for
> > > > > > > > qt5. Imported from meta-qt5 layer.
> > > > > > > > 
> > > > > > > > Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
> > > > > > > > ---
> > > > > > > >  .../gstreamer/gstreamer1.0-plugins-
> > > > > > > > good_1.16.2.bb                  | 7 +------
> > > > > > > >  1 file changed, 1 insertion(+), 6 deletions(-)
> > > > > > > > 
> > > > > > > > diff --git a/meta/recipes-
> > > > > > > > multimedia/gstreamer/gstreamer1.0-
> > > > > > > > plugins-good_1.16.2.bb b/meta/recipes-
> > > > > > > > multimedia/gstreamer/gstreamer1.0-plugins-good_1.16.2.bb
> > > > > > > > index f3e0cee..8b34111 100644
> > > > > > > > --- a/meta/recipes-multimedia/gstreamer/gstreamer1.0-
> > > > > > > > plugins-
> > > > > > > > good_1.16.2.bb
> > > > > > > > +++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0-
> > > > > > > > plugins-
> > > > > > > > good_1.16.2.bb
> > > > > > > > @@ -42,6 +42,7 @@ PACKAGECONFIG[libpng]     = "-
> > > > > > > > Dpng=enabled,-
> > > > > > > > Dpng=disabled,libpng"
> > > > > > > >  PACKAGECONFIG[libv4l2]    = "-Dv4l2-libv4l2=enabled,-
> > > > > > > > Dv4l2-
> > > > > > > > libv4l2=disabled,v4l-utils"
> > > > > > > >  PACKAGECONFIG[mpg123]     = "-Dmpg123=enabled,-
> > > > > > > > Dmpg123=disabled,mpg123"
> > > > > > > >  PACKAGECONFIG[pulseaudio] = "-Dpulse=enabled,-
> > > > > > > > Dpulse=disabled,pulseaudio"
> > > > > > > > +PACKAGECONFIG[qt5]        = "-Dqt5=enabled,-
> > > > > > > > Dqt5=disabled,qtbase
> > > > > > > > qtdeclarative qtbase-native"
> > > > > > > 
> > > > > > > Does it make oe-core depend on meta-qt5 layer?
> > > > > > > 
> > > > > > > What is the policy here for having inter-layer dependencies
> > > > > > > in
> > > > > > > DEPENDS vs. PACKAGECONFIG without explicitly listing them
> > > > > > > in
> > > > > > > LAYERDEPENDS?
> > > > > > 
> > > > > > We have a clear policy that listing such options is ok as
> > > > > > long as
> > > > > > its
> > > > > > not enabled by default.
> > > > > 
> > > > > Richard,
> > > > > 
> > > > > This is good, thank you for confirming. Do you have a link
> > > > > where this
> > > > > is clearly explained? Thanks again.
> > > > 
> > > > Its come up many times over the years and we've been consistent
> > > > about
> > > > it. I don't have a link but there has been mailing list
> > > > discussion and
> > > > perhaps TSC discussion long ago, I simply don't remember. There
> > > > are
> > > > many examples of that in OE-Core.
> > > > 
> > > > The alternative is forcing more into bbappends which doesn't seem
> > > > to
> > > > gain anything (PACKAGECONFIG itself could be changed from distro
> > > > config
> > > > for example).
> > > > 
> > > > Its also easy to catch bad defaults since the recipes would no
> > > > longer
> > > > parse due to missing dependencies which we'd quickly spot.
> > > 
> > > Richard,
> > > 
> > > Yes, yes, I understanf all that from a technical perspective and
> > > agree with 
> > > it, but I was thinking about a more clear definition of this policy
> > > to be able 
> > > to point anyone having such questions in the future...
> > 
> > BTW, I don't remember discussing this at YP TSC... Maybe OE TSC
> > covered this in the past?
> 
> Metadata architecture decision would be the OE TSC and "TSC discussion
> long ago" means something from several years ago.

Thought so - were there any meeting minutes from back then? Sorry for being so 
persistent, just trying to find some paper trail... :)

-- 
Denys

  reply	other threads:[~2020-03-24 19:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-21  2:41 [PATCH v3 1/2] gstreamer1.0-plugins-good: change EXTRA_OECONF -> EXTRA_OEMESON Anuj Mittal
2020-02-21  2:41 ` [PATCH 2/2] gstreamer1.0-plugins-good: add qt5 PACKAGECONFIG Anuj Mittal
2020-03-24 17:58   ` [OE-core] " Denys Dmytriyenko
2020-03-24 18:07     ` Richard Purdie
2020-03-24 18:12       ` Denys Dmytriyenko
2020-03-24 18:15         ` Richard Purdie
2020-03-24 18:33           ` Denys Dmytriyenko
2020-03-24 18:45             ` Richard Purdie
     [not found]           ` <15FF5122E920BDAA.24006@lists.openembedded.org>
2020-03-24 18:43             ` Denys Dmytriyenko
2020-03-24 19:29               ` Richard Purdie
2020-03-24 19:32                 ` Denys Dmytriyenko [this message]
2020-03-24 19:57                   ` Richard Purdie
2020-03-24 22:12                     ` Denys Dmytriyenko
2020-03-24 22:37                       ` Richard Purdie
2020-04-12 18:46                         ` Denys Dmytriyenko
2020-04-12 18:49                           ` Richard Purdie
2020-02-21  3:01 ` ✗ patchtest: failure for "[v3] gstreamer1.0-plugins-good..." and 1 more Patchwork

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=20200324193222.GA1578@denix.org \
    --to=denis@denix.org \
    --cc=anuj.mittal@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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