On Thu, Mar 21, 2024 at 5:55 PM Randy MacLeod via
lists.openembedded.org
<randy.macleod=windriver....@lists.openembedded.org> wrote:
>
> Would the new license scheme described here:
>
> https://redis.com/blog/redis-adopts-dual-source-available-licensing/
>
> prevent us from accepting the 7.4 release? I suspect it should but I need 
> more time to
> read the new terms.
>

Good point. I saw the announcement today as well. I think we need to
certainly change to
use new license, if we can distribute it or not, perhaps it needs some
closer look.

> ../Randy
>
>
> On 2024-01-30 1:23 p.m., Martin Jansa via lists.openembedded.org wrote:
>
> On Tue, Jan 30, 2024 at 6:28 PM Khem Raj <raj.k...@gmail.com> wrote:
>>
>> On 1/30/24 2:34 AM, Martin Jansa wrote:
>> > * accidentally dropped in:
>> >    
>> > https://git.openembedded.org/meta-openembedded/commit/?id=e91fa668ed1dd4a3f6b06bcb099f70dbdd2a50b4
>> > ---
>> >   .../lua-update-Makefile-to-use-environment-build-setting.patch  | 2 ++
>> >   1 file changed, 2 insertions(+)
>> >
>> > diff --git 
>> > a/meta-oe/recipes-extended/redis/redis-7.2.4/lua-update-Makefile-to-use-environment-build-setting.patch
>> >  
>> > b/meta-oe/recipes-extended/redis/redis-7.2.4/lua-update-Makefile-to-use-environment-build-setting.patch
>> > index b562e2522c..48a8bb5b4b 100644
>> > --- 
>> > a/meta-oe/recipes-extended/redis/redis-7.2.4/lua-update-Makefile-to-use-environment-build-setting.patch
>> > +++ 
>> > b/meta-oe/recipes-extended/redis/redis-7.2.4/lua-update-Makefile-to-use-environment-build-setting.patch
>> > @@ -16,6 +16,8 @@ updated to work wtih 6.2.1
>> >   Signed-off-by: Yi Fan Yu <yifan...@windriver.com>
>> >
>> >   ---
>> > +Upstream-Status: Pending
>>
>> I think it might be better to move it above the scissor to avoid getting
>> lost in next devtool based upgrade.
>
>
> As you wish, resent all 3 as v2 with it moved.
>
> FWIW: in 
> https://github.com/webosose/meta-webosose/commit/2c78e37ad9ceb9e236c03b44cca5b38e9d9eb2fc
>  I've moved all Upstream-Statuses in LGE layers bellow, because too often 
> developers applied them with Upstream-Status into the component source git 
> repo where it doesn't belong and then it was already too late to remove it 
> there (while with Upstream-Status lost in rebase/devtool there is still time 
> to get warning from QA check and once this check is enabled by default in all 
> the builds it will prevent people overlooking this by accident).
>
>
>
> --
> # Randy MacLeod
> # Wind River Linux
>
>
> 
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#109508): 
https://lists.openembedded.org/g/openembedded-devel/message/109508
Mute This Topic: https://lists.openembedded.org/mt/105077570/21656
Group Owner: openembedded-devel+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to