From: Adrian Bunk <bunk@stusta.de>
To: Tim Orling <ticotimo@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/4] scons.bbclass: use python3-scons
Date: Sun, 23 Jun 2019 22:24:39 +0300 [thread overview]
Message-ID: <20190623192439.GA11669@localhost> (raw)
In-Reply-To: <CANx9H-C63ech2pPxYwirWJRE4-p9uQTA0zcBAzepYK0L4mth0Q@mail.gmail.com>
On Sun, Jun 23, 2019 at 09:44:07AM -0700, Tim Orling wrote:
> On Sat, Jun 22, 2019 at 5:03 PM Khem Raj <raj.khem@gmail.com> wrote:
>
> >
> >
> > On Sat, Jun 22, 2019 at 1:58 AM Adrian Bunk <bunk@stusta.de> wrote:
> >
> >> On Thu, Jun 20, 2019 at 09:27:15PM -0600, Khem Raj wrote:
> >> > On Thu, Jun 20, 2019 at 6:18 PM Tim Orling <ticotimo@gmail.com> wrote:
> >> >...
> >> > > Latest mongo release appears to be 4.3.0 and appears to support
> >> python3:
> >> > >
> >> > >
> >> > >
> >> https://github.com/mongodb/mongo/blob/89e7419a897b2270931c9c029abf6de555d83e0f/SConstruct
> >> > >
> >> > > Is this an aceptable upgrade? I am not savvy on which versions are
> >> > > desirable.
> >> >
> >> > Yes for master this upgrade is fine
> >>
> >> Are you approving the changed licence for OE,
> >> or were you not aware that this was the question?
> >>
> >
> > What has changed between 4.0.6 and 4.3.0 w.r.t. licensing ?
> >
>
> The Server Side License is already in 4.0.6
> https://github.com/mongodb/mongo/blob/caa42a1f75a56c7643d0b68d3880444375ec42e3/LICENSE-Community.txt
>...
Ah sorry, I missed that.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-06-23 19:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 23:47 [PATCH 0/4] Move SCons to Python 3 Tim Orling
2019-06-07 23:47 ` [PATCH 1/4] python3-scons-{native}: add recipe for v3.0.5 Tim Orling
2019-06-08 0:56 ` Tim Orling
2019-06-07 23:47 ` [PATCH 2/4] scons.bbclass: use python3-scons Tim Orling
2019-06-20 13:36 ` Khem Raj
2019-06-21 0:18 ` Tim Orling
2019-06-21 3:27 ` Khem Raj
2019-06-22 8:58 ` Adrian Bunk
2019-06-23 0:03 ` Khem Raj
2019-06-23 16:44 ` Tim Orling
2019-06-23 19:24 ` Adrian Bunk [this message]
2019-06-24 1:49 ` Tim Orling
2019-06-24 2:41 ` Alistair Francis
2019-06-24 8:20 ` Adrian Bunk
2019-06-24 17:27 ` Alistair Francis
2019-06-07 23:47 ` [PATCH 3/4] serf: switch to python3-scons-native Tim Orling
2019-06-10 5:10 ` Mittal, Anuj
2019-06-10 5:22 ` Tim Orling
2019-06-12 20:52 ` Khem Raj
2019-06-07 23:47 ` [PATCH 4/4] oeqa/runtime: add simple test for scons Tim Orling
2019-06-08 3:54 ` ✗ patchtest: failure for Move SCons to Python 3 Patchwork
2019-06-08 4:04 ` Tim Orling
2019-06-08 7:13 ` [PATCH 0/4] " Burton, Ross
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=20190623192439.GA11669@localhost \
--to=bunk@stusta.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=ticotimo@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox