From: "Denys Dmytriyenko" <denis@denix.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
Michael Halstead <mhalstead@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 2/2] gstreamer1.0-plugins-good: add qt5 PACKAGECONFIG
Date: Tue, 24 Mar 2020 18:12:31 -0400 [thread overview]
Message-ID: <20200324221231.GB1578@denix.org> (raw)
In-Reply-To: <fe9b411737f87754311de2c607656b8ac74aee86.camel@linuxfoundation.org>
On Tue, Mar 24, 2020 at 07:57:27PM +0000, Richard Purdie wrote:
> On Tue, 2020-03-24 at 15:32 -0400, Denys Dmytriyenko wrote:
> > 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:
> > > > > 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... :)
>
> Yes, there is a record. You can find it quite easily. I don't need to
> do this for you...
All I could find is OE TSC minutes from 7 May 2013 referring to some related
list discussion:
https://lists.openembedded.org/g/tsc/message/369?p=,,,20,0,0,0::Created,,PACKAGECONFIG,20,2,0,72188707
(9:47:21 AM) RP: bluelightning: I think this was to PACKAGECONFIG more recipes
(9:47:28 AM) bluelightning: ah ok
(9:47:36 AM) RP: bluelightning: remove the need to bbappend, have
people set mode config options
(9:47:51 AM) bluelightning: and PACKAGECONFIG to enable deps on things
outside OE-Core as well presumably
(9:48:01 AM) bluelightning: (as discussed on the ml a few weeks ago)
(9:48:06 AM) fray: yup
I spent last couple hours digging through my archives of openembedded-core and
openembedded-devel lists around that time (Spring 2013), but besides general
move to enable PACKAGECONFIG in recipes, I didn't see anything specific about
crossing layer boundaries by PACKAGECONFIG dependencies, unfortunately. And it
was a wild time - all the energy, extra activity, conflicts, flamewars - that
definitely brought up some memories re-reading those discussions again... :)
BTW, all the links on this page are now dead, since they point to the old
mailman/pipermail archives:
https://www.openembedded.org/wiki/TSC
Michael,
Is there any way to correct the links in bulk or preserve the old archives, so
the old links would still work?
--
Denys
next prev parent reply other threads:[~2020-03-24 22:12 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
2020-03-24 19:57 ` Richard Purdie
2020-03-24 22:12 ` Denys Dmytriyenko [this message]
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=20200324221231.GB1578@denix.org \
--to=denis@denix.org \
--cc=mhalstead@linuxfoundation.org \
--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