Re: [yocto] [meta-lts-mixins][dunfell/go PATCH 1/4] Initial commit: add license, readme and layer config.

Re: [yocto] [meta-lts-mixins][dunfell/go PATCH 1/4] Initial commit: add license, readme and layer config.

[Alexander Kanavin]

[-- Attachment #1: Type: text/plain, Size: 4252 bytes --]

A question specifically to Denys, how can I actually get this into the
mixin repo, and have commit rights to the branch? We've tested this quite
well in private, and there are further enhancements coming up.

Alex

On Thu, 27 Jan 2022 at 15:43, Alexander Kanavin via lists.yoctoproject.org
<alex.kanavin=gmail.com@lists.yoctoproject.org> wrote:

> Reviewed-by: Martin Kaistra <martin.kaistra@linutronix.de>
> Signed-off-by: Alexander Kanavin <alex@linutronix.de>
> ---
>  COPYING.MIT     | 17 +++++++++++++++++
>  README          | 23 +++++++++++++++++++++++
>  conf/layer.conf | 19 +++++++++++++++++++
>  3 files changed, 59 insertions(+)
>  create mode 100644 COPYING.MIT
>  create mode 100644 README
>  create mode 100644 conf/layer.conf
>
> diff --git a/COPYING.MIT b/COPYING.MIT
> new file mode 100644
> index 0000000..fb950dc
> --- /dev/null
> +++ b/COPYING.MIT
> @@ -0,0 +1,17 @@
> +Permission is hereby granted, free of charge, to any person obtaining a
> copy
> +of this software and associated documentation files (the "Software"), to
> deal
> +in the Software without restriction, including without limitation the
> rights
> +to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
> +copies of the Software, and to permit persons to whom the Software is
> +furnished to do so, subject to the following conditions:
> +
> +The above copyright notice and this permission notice shall be included
> in
> +all copies or substantial portions of the Software.
> +
> +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
> OR
> +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
> +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
> THE
> +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
> +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
> FROM,
> +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
> +THE SOFTWARE.
> diff --git a/README b/README
> new file mode 100644
> index 0000000..5b22b72
> --- /dev/null
> +++ b/README
> @@ -0,0 +1,23 @@
> +"Mixin" layer for adding latest Go toolchain versions into the Yocto
> Project LTS.
> +
> +At the time Dunfell was released in April 2020, Go 1.14 was the latest
> version
> +and officially Dunfell supports only that. This thin special-purpose mixin
> +layer is meant to address this issue by backporting Go recipes from the
> master
> +branch of openembedded-core.
> +
> +You can see what Go versions are provided by listing recipes-devtools/
> content.
> +
> +Including the layer automatically picks up the latest Go version;
> different versions
> +need to be set explicitly by adding the following line to your distro
> config
> +or local.conf:
> +
> +GOVERSION = "1.16%"
> +
> +Please note: enabling these newer Go versions makes docker from dunfell
> branch
> +of meta-virtualization unbuildable as it is too old. If you need a
> working docker
> +recipe, you can use the supplementary 'dunfell/docker' layer from this
> meta-lts-mixin
> +repository.
> +
> +
> +Maintainers:
> +Alexander Kanavin <alex@linutronix.de>
> diff --git a/conf/layer.conf b/conf/layer.conf
> new file mode 100644
> index 0000000..5f74224
> --- /dev/null
> +++ b/conf/layer.conf
> @@ -0,0 +1,19 @@
> +# We have a conf and classes directory, append to BBPATH
> +BBPATH .= ":${LAYERDIR}"
> +
> +# We have a recipes directory, add to BBFILES
> +BBFILES += "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend"
> +
> +BBFILE_COLLECTIONS += "lts-go-mixin"
> +BBFILE_PATTERN_lts-go-mixin := "^${LAYERDIR}/"
> +BBFILE_PRIORITY_lts-go-mixin = "6"
> +
> +LAYERSERIES_COMPAT_lts-go-mixin = "dunfell"
> +
> +LAYERDEPENDS_lts-go-mixin = " \
> +    core \
> +"
> +
> +GOVERSION ?= "1.17%"
> +PREFERRED_PROVIDER_go-native = "go-binary-native"
> +
> --
> 2.20.1
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#55990):
> https://lists.yoctoproject.org/g/yocto/message/55990
> Mute This Topic: https://lists.yoctoproject.org/mt/88722205/1686489
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [
> alex.kanavin@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>

[-- Attachment #2: Type: text/html, Size: 5685 bytes --]

Re: [yocto] [meta-lts-mixins][dunfell/go PATCH 1/4] Initial commit: add license, readme and layer config.

[Khem Raj]

On Thu, Jan 27, 2022 at 9:07 AM Alexander Kanavin
<alex.kanavin@gmail.com> wrote:
>
> A question specifically to Denys, how can I actually get this into the mixin repo, and have commit rights to the branch? We've tested this quite well in private, and there are further enhancements coming up.
>

this could be an independent layer too.


> Alex
>
> On Thu, 27 Jan 2022 at 15:43, Alexander Kanavin via lists.yoctoproject.org <alex.kanavin=gmail.com@lists.yoctoproject.org> wrote:
>>
>> Reviewed-by: Martin Kaistra <martin.kaistra@linutronix.de>
>> Signed-off-by: Alexander Kanavin <alex@linutronix.de>
>> ---
>>  COPYING.MIT     | 17 +++++++++++++++++
>>  README          | 23 +++++++++++++++++++++++
>>  conf/layer.conf | 19 +++++++++++++++++++
>>  3 files changed, 59 insertions(+)
>>  create mode 100644 COPYING.MIT
>>  create mode 100644 README
>>  create mode 100644 conf/layer.conf
>>
>> diff --git a/COPYING.MIT b/COPYING.MIT
>> new file mode 100644
>> index 0000000..fb950dc
>> --- /dev/null
>> +++ b/COPYING.MIT
>> @@ -0,0 +1,17 @@
>> +Permission is hereby granted, free of charge, to any person obtaining a copy
>> +of this software and associated documentation files (the "Software"), to deal
>> +in the Software without restriction, including without limitation the rights
>> +to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
>> +copies of the Software, and to permit persons to whom the Software is
>> +furnished to do so, subject to the following conditions:
>> +
>> +The above copyright notice and this permission notice shall be included in
>> +all copies or substantial portions of the Software.
>> +
>> +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
>> +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
>> +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
>> +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
>> +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
>> +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
>> +THE SOFTWARE.
>> diff --git a/README b/README
>> new file mode 100644
>> index 0000000..5b22b72
>> --- /dev/null
>> +++ b/README
>> @@ -0,0 +1,23 @@
>> +"Mixin" layer for adding latest Go toolchain versions into the Yocto Project LTS.
>> +
>> +At the time Dunfell was released in April 2020, Go 1.14 was the latest version
>> +and officially Dunfell supports only that. This thin special-purpose mixin
>> +layer is meant to address this issue by backporting Go recipes from the master
>> +branch of openembedded-core.
>> +
>> +You can see what Go versions are provided by listing recipes-devtools/ content.
>> +
>> +Including the layer automatically picks up the latest Go version; different versions
>> +need to be set explicitly by adding the following line to your distro config
>> +or local.conf:
>> +
>> +GOVERSION = "1.16%"
>> +
>> +Please note: enabling these newer Go versions makes docker from dunfell branch
>> +of meta-virtualization unbuildable as it is too old. If you need a working docker
>> +recipe, you can use the supplementary 'dunfell/docker' layer from this meta-lts-mixin
>> +repository.
>> +
>> +
>> +Maintainers:
>> +Alexander Kanavin <alex@linutronix.de>
>> diff --git a/conf/layer.conf b/conf/layer.conf
>> new file mode 100644
>> index 0000000..5f74224
>> --- /dev/null
>> +++ b/conf/layer.conf
>> @@ -0,0 +1,19 @@
>> +# We have a conf and classes directory, append to BBPATH
>> +BBPATH .= ":${LAYERDIR}"
>> +
>> +# We have a recipes directory, add to BBFILES
>> +BBFILES += "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend"
>> +
>> +BBFILE_COLLECTIONS += "lts-go-mixin"
>> +BBFILE_PATTERN_lts-go-mixin := "^${LAYERDIR}/"
>> +BBFILE_PRIORITY_lts-go-mixin = "6"
>> +
>> +LAYERSERIES_COMPAT_lts-go-mixin = "dunfell"
>> +
>> +LAYERDEPENDS_lts-go-mixin = " \
>> +    core \
>> +"
>> +
>> +GOVERSION ?= "1.17%"
>> +PREFERRED_PROVIDER_go-native = "go-binary-native"
>> +
>> --
>> 2.20.1
>>
>>
>>
>>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> You automatically follow any topics you start or reply to.
> View/Reply Online (#56001): https://lists.yoctoproject.org/g/yocto/message/56001
> Mute This Topic: https://lists.yoctoproject.org/mt/88722205/1997914
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [raj.khem@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>

Re: [yocto] [meta-lts-mixins][dunfell/go PATCH 1/4] Initial commit: add license, readme and layer config.

[Denys Dmytriyenko]

On Thu, Jan 27, 2022 at 06:07:06PM +0100, Alexander Kanavin wrote:
> A question specifically to Denys, how can I actually get this into the
> mixin repo, and have commit rights to the branch? We've tested this quite
> well in private, and there are further enhancements coming up.

Michael,

Would it be possible to create 2 additional branches in the meta-lts-mixins 
repository at https://git.yoctoproject.org/meta-lts-mixins/ called 
"dunfell/go" and also "dunfell/docker" and give Alex push rights to them?

Please let us know, thanks a lot!

-- 
Denys


> On Thu, 27 Jan 2022 at 15:43, Alexander Kanavin via lists.yoctoproject.org
> <alex.kanavin=gmail.com@lists.yoctoproject.org> wrote:
> 
> > Reviewed-by: Martin Kaistra <martin.kaistra@linutronix.de>
> > Signed-off-by: Alexander Kanavin <alex@linutronix.de>
> > ---
> >  COPYING.MIT     | 17 +++++++++++++++++
> >  README          | 23 +++++++++++++++++++++++
> >  conf/layer.conf | 19 +++++++++++++++++++
> >  3 files changed, 59 insertions(+)
> >  create mode 100644 COPYING.MIT
> >  create mode 100644 README
> >  create mode 100644 conf/layer.conf
> >
> > diff --git a/COPYING.MIT b/COPYING.MIT
> > new file mode 100644
> > index 0000000..fb950dc
> > --- /dev/null
> > +++ b/COPYING.MIT
> > @@ -0,0 +1,17 @@
> > +Permission is hereby granted, free of charge, to any person obtaining a
> > copy
> > +of this software and associated documentation files (the "Software"), to
> > deal
> > +in the Software without restriction, including without limitation the
> > rights
> > +to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
> > +copies of the Software, and to permit persons to whom the Software is
> > +furnished to do so, subject to the following conditions:
> > +
> > +The above copyright notice and this permission notice shall be included
> > in
> > +all copies or substantial portions of the Software.
> > +
> > +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
> > OR
> > +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
> > +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
> > THE
> > +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
> > +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
> > FROM,
> > +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
> > +THE SOFTWARE.
> > diff --git a/README b/README
> > new file mode 100644
> > index 0000000..5b22b72
> > --- /dev/null
> > +++ b/README
> > @@ -0,0 +1,23 @@
> > +"Mixin" layer for adding latest Go toolchain versions into the Yocto
> > Project LTS.
> > +
> > +At the time Dunfell was released in April 2020, Go 1.14 was the latest
> > version
> > +and officially Dunfell supports only that. This thin special-purpose mixin
> > +layer is meant to address this issue by backporting Go recipes from the
> > master
> > +branch of openembedded-core.
> > +
> > +You can see what Go versions are provided by listing recipes-devtools/
> > content.
> > +
> > +Including the layer automatically picks up the latest Go version;
> > different versions
> > +need to be set explicitly by adding the following line to your distro
> > config
> > +or local.conf:
> > +
> > +GOVERSION = "1.16%"
> > +
> > +Please note: enabling these newer Go versions makes docker from dunfell
> > branch
> > +of meta-virtualization unbuildable as it is too old. If you need a
> > working docker
> > +recipe, you can use the supplementary 'dunfell/docker' layer from this
> > meta-lts-mixin
> > +repository.
> > +
> > +
> > +Maintainers:
> > +Alexander Kanavin <alex@linutronix.de>
> > diff --git a/conf/layer.conf b/conf/layer.conf
> > new file mode 100644
> > index 0000000..5f74224
> > --- /dev/null
> > +++ b/conf/layer.conf
> > @@ -0,0 +1,19 @@
> > +# We have a conf and classes directory, append to BBPATH
> > +BBPATH .= ":${LAYERDIR}"
> > +
> > +# We have a recipes directory, add to BBFILES
> > +BBFILES += "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend"
> > +
> > +BBFILE_COLLECTIONS += "lts-go-mixin"
> > +BBFILE_PATTERN_lts-go-mixin := "^${LAYERDIR}/"
> > +BBFILE_PRIORITY_lts-go-mixin = "6"
> > +
> > +LAYERSERIES_COMPAT_lts-go-mixin = "dunfell"
> > +
> > +LAYERDEPENDS_lts-go-mixin = " \
> > +    core \
> > +"
> > +
> > +GOVERSION ?= "1.17%"
> > +PREFERRED_PROVIDER_go-native = "go-binary-native"
> > +
> > --
> > 2.20.1

Re: [yocto] [meta-lts-mixins][dunfell/go PATCH 1/4] Initial commit: add license, readme and layer config.

[Khem Raj]

[-- Attachment #1: Type: text/plain, Size: 5299 bytes --]

On Thu, Jan 27, 2022 at 12:06 PM Denys Dmytriyenko <denis@denix.org> wrote:

> On Thu, Jan 27, 2022 at 06:07:06PM +0100, Alexander Kanavin wrote:
> > A question specifically to Denys, how can I actually get this into the
> > mixin repo, and have commit rights to the branch? We've tested this quite
> > well in private, and there are further enhancements coming up.
>
> Michael,
>
> Would it be possible to create 2 additional branches in the
> meta-lts-mixins
> repository at https://git.yoctoproject.org/meta-lts-mixins/ called
> "dunfell/go" and also "dunfell/docker" and give Alex push rights to them?


How would one use new version of  both  go and say kernel in a project


>
> Please let us know, thanks a lot!
>
> --
> Denys
>
>
> > On Thu, 27 Jan 2022 at 15:43, Alexander Kanavin via
> lists.yoctoproject.org
> > <alex.kanavin=gmail.com@lists.yoctoproject.org> wrote:
> >
> > > Reviewed-by: Martin Kaistra <martin.kaistra@linutronix.de>
> > > Signed-off-by: Alexander Kanavin <alex@linutronix.de>
> > > ---
> > >  COPYING.MIT     | 17 +++++++++++++++++
> > >  README          | 23 +++++++++++++++++++++++
> > >  conf/layer.conf | 19 +++++++++++++++++++
> > >  3 files changed, 59 insertions(+)
> > >  create mode 100644 COPYING.MIT
> > >  create mode 100644 README
> > >  create mode 100644 conf/layer.conf
> > >
> > > diff --git a/COPYING.MIT b/COPYING.MIT
> > > new file mode 100644
> > > index 0000000..fb950dc
> > > --- /dev/null
> > > +++ b/COPYING.MIT
> > > @@ -0,0 +1,17 @@
> > > +Permission is hereby granted, free of charge, to any person obtaining
> a
> > > copy
> > > +of this software and associated documentation files (the "Software"),
> to
> > > deal
> > > +in the Software without restriction, including without limitation the
> > > rights
> > > +to use, copy, modify, merge, publish, distribute, sublicense, and/or
> sell
> > > +copies of the Software, and to permit persons to whom the Software is
> > > +furnished to do so, subject to the following conditions:
> > > +
> > > +The above copyright notice and this permission notice shall be
> included
> > > in
> > > +all copies or substantial portions of the Software.
> > > +
> > > +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
> EXPRESS
> > > OR
> > > +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
> MERCHANTABILITY,
> > > +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT
> SHALL
> > > THE
> > > +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
> > > +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
> ARISING
> > > FROM,
> > > +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
> DEALINGS IN
> > > +THE SOFTWARE.
> > > diff --git a/README b/README
> > > new file mode 100644
> > > index 0000000..5b22b72
> > > --- /dev/null
> > > +++ b/README
> > > @@ -0,0 +1,23 @@
> > > +"Mixin" layer for adding latest Go toolchain versions into the Yocto
> > > Project LTS.
> > > +
> > > +At the time Dunfell was released in April 2020, Go 1.14 was the latest
> > > version
> > > +and officially Dunfell supports only that. This thin special-purpose
> mixin
> > > +layer is meant to address this issue by backporting Go recipes from
> the
> > > master
> > > +branch of openembedded-core.
> > > +
> > > +You can see what Go versions are provided by listing recipes-devtools/
> > > content.
> > > +
> > > +Including the layer automatically picks up the latest Go version;
> > > different versions
> > > +need to be set explicitly by adding the following line to your distro
> > > config
> > > +or local.conf:
> > > +
> > > +GOVERSION = "1.16%"
> > > +
> > > +Please note: enabling these newer Go versions makes docker from
> dunfell
> > > branch
> > > +of meta-virtualization unbuildable as it is too old. If you need a
> > > working docker
> > > +recipe, you can use the supplementary 'dunfell/docker' layer from this
> > > meta-lts-mixin
> > > +repository.
> > > +
> > > +
> > > +Maintainers:
> > > +Alexander Kanavin <alex@linutronix.de>
> > > diff --git a/conf/layer.conf b/conf/layer.conf
> > > new file mode 100644
> > > index 0000000..5f74224
> > > --- /dev/null
> > > +++ b/conf/layer.conf
> > > @@ -0,0 +1,19 @@
> > > +# We have a conf and classes directory, append to BBPATH
> > > +BBPATH .= ":${LAYERDIR}"
> > > +
> > > +# We have a recipes directory, add to BBFILES
> > > +BBFILES += "${LAYERDIR}/recipes*/*/*.bb
> ${LAYERDIR}/recipes*/*/*.bbappend"
> > > +
> > > +BBFILE_COLLECTIONS += "lts-go-mixin"
> > > +BBFILE_PATTERN_lts-go-mixin := "^${LAYERDIR}/"
> > > +BBFILE_PRIORITY_lts-go-mixin = "6"
> > > +
> > > +LAYERSERIES_COMPAT_lts-go-mixin = "dunfell"
> > > +
> > > +LAYERDEPENDS_lts-go-mixin = " \
> > > +    core \
> > > +"
> > > +
> > > +GOVERSION ?= "1.17%"
> > > +PREFERRED_PROVIDER_go-native = "go-binary-native"
> > > +
> > > --
> > > 2.20.1
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> You automatically follow any topics you start or reply to.
> View/Reply Online (#56003):
> https://lists.yoctoproject.org/g/yocto/message/56003
> Unfollow This Topic: https://lists.yoctoproject.org/unft/88722205/1997914
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [
> raj.khem@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>

[-- Attachment #2: Type: text/html, Size: 7841 bytes --]

Re: [yocto] [meta-lts-mixins][dunfell/go PATCH 1/4] Initial commit: add license, readme and layer config.

[Alexander Kanavin]

[-- Attachment #1: Type: text/plain, Size: 5765 bytes --]

On Thu, 27 Jan 2022 at 22:04, Khem Raj <raj.khem@gmail.com> wrote:

>
>
> On Thu, Jan 27, 2022 at 12:06 PM Denys Dmytriyenko <denis@denix.org>
> wrote:
>
>> On Thu, Jan 27, 2022 at 06:07:06PM +0100, Alexander Kanavin wrote:
>> > A question specifically to Denys, how can I actually get this into the
>> > mixin repo, and have commit rights to the branch? We've tested this
>> quite
>> > well in private, and there are further enhancements coming up.
>>
>> Michael,
>>
>> Would it be possible to create 2 additional branches in the
>> meta-lts-mixins
>> repository at https://git.yoctoproject.org/meta-lts-mixins/ called
>> "dunfell/go" and also "dunfell/docker" and give Alex push rights to them?
>
>
> How would one use new version of  both  go and say kernel in a project
>

Checkout the branches from the same repo into two different directories.
Yes this is unusual, and slightly confusing. But that way the branches can
be maintained and included into builds independently.

Alex



>
>
>>
>> Please let us know, thanks a lot!
>>
>> --
>> Denys
>>
>>
>> > On Thu, 27 Jan 2022 at 15:43, Alexander Kanavin via
>> lists.yoctoproject.org
>> > <alex.kanavin=gmail.com@lists.yoctoproject.org> wrote:
>> >
>> > > Reviewed-by: Martin Kaistra <martin.kaistra@linutronix.de>
>> > > Signed-off-by: Alexander Kanavin <alex@linutronix.de>
>> > > ---
>> > >  COPYING.MIT     | 17 +++++++++++++++++
>> > >  README          | 23 +++++++++++++++++++++++
>> > >  conf/layer.conf | 19 +++++++++++++++++++
>> > >  3 files changed, 59 insertions(+)
>> > >  create mode 100644 COPYING.MIT
>> > >  create mode 100644 README
>> > >  create mode 100644 conf/layer.conf
>> > >
>> > > diff --git a/COPYING.MIT b/COPYING.MIT
>> > > new file mode 100644
>> > > index 0000000..fb950dc
>> > > --- /dev/null
>> > > +++ b/COPYING.MIT
>> > > @@ -0,0 +1,17 @@
>> > > +Permission is hereby granted, free of charge, to any person
>> obtaining a
>> > > copy
>> > > +of this software and associated documentation files (the
>> "Software"), to
>> > > deal
>> > > +in the Software without restriction, including without limitation the
>> > > rights
>> > > +to use, copy, modify, merge, publish, distribute, sublicense, and/or
>> sell
>> > > +copies of the Software, and to permit persons to whom the Software is
>> > > +furnished to do so, subject to the following conditions:
>> > > +
>> > > +The above copyright notice and this permission notice shall be
>> included
>> > > in
>> > > +all copies or substantial portions of the Software.
>> > > +
>> > > +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
>> EXPRESS
>> > > OR
>> > > +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
>> MERCHANTABILITY,
>> > > +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT
>> SHALL
>> > > THE
>> > > +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR
>> OTHER
>> > > +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
>> ARISING
>> > > FROM,
>> > > +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
>> DEALINGS IN
>> > > +THE SOFTWARE.
>> > > diff --git a/README b/README
>> > > new file mode 100644
>> > > index 0000000..5b22b72
>> > > --- /dev/null
>> > > +++ b/README
>> > > @@ -0,0 +1,23 @@
>> > > +"Mixin" layer for adding latest Go toolchain versions into the Yocto
>> > > Project LTS.
>> > > +
>> > > +At the time Dunfell was released in April 2020, Go 1.14 was the
>> latest
>> > > version
>> > > +and officially Dunfell supports only that. This thin special-purpose
>> mixin
>> > > +layer is meant to address this issue by backporting Go recipes from
>> the
>> > > master
>> > > +branch of openembedded-core.
>> > > +
>> > > +You can see what Go versions are provided by listing
>> recipes-devtools/
>> > > content.
>> > > +
>> > > +Including the layer automatically picks up the latest Go version;
>> > > different versions
>> > > +need to be set explicitly by adding the following line to your distro
>> > > config
>> > > +or local.conf:
>> > > +
>> > > +GOVERSION = "1.16%"
>> > > +
>> > > +Please note: enabling these newer Go versions makes docker from
>> dunfell
>> > > branch
>> > > +of meta-virtualization unbuildable as it is too old. If you need a
>> > > working docker
>> > > +recipe, you can use the supplementary 'dunfell/docker' layer from
>> this
>> > > meta-lts-mixin
>> > > +repository.
>> > > +
>> > > +
>> > > +Maintainers:
>> > > +Alexander Kanavin <alex@linutronix.de>
>> > > diff --git a/conf/layer.conf b/conf/layer.conf
>> > > new file mode 100644
>> > > index 0000000..5f74224
>> > > --- /dev/null
>> > > +++ b/conf/layer.conf
>> > > @@ -0,0 +1,19 @@
>> > > +# We have a conf and classes directory, append to BBPATH
>> > > +BBPATH .= ":${LAYERDIR}"
>> > > +
>> > > +# We have a recipes directory, add to BBFILES
>> > > +BBFILES += "${LAYERDIR}/recipes*/*/*.bb
>> ${LAYERDIR}/recipes*/*/*.bbappend"
>> > > +
>> > > +BBFILE_COLLECTIONS += "lts-go-mixin"
>> > > +BBFILE_PATTERN_lts-go-mixin := "^${LAYERDIR}/"
>> > > +BBFILE_PRIORITY_lts-go-mixin = "6"
>> > > +
>> > > +LAYERSERIES_COMPAT_lts-go-mixin = "dunfell"
>> > > +
>> > > +LAYERDEPENDS_lts-go-mixin = " \
>> > > +    core \
>> > > +"
>> > > +
>> > > +GOVERSION ?= "1.17%"
>> > > +PREFERRED_PROVIDER_go-native = "go-binary-native"
>> > > +
>> > > --
>> > > 2.20.1
>>
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>> You automatically follow any topics you start or reply to.
>> View/Reply Online (#56003):
>> https://lists.yoctoproject.org/g/yocto/message/56003
>> Unfollow This Topic: https://lists.yoctoproject.org/unft/88722205/1997914
>> Group Owner: yocto+owner@lists.yoctoproject.org
>> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [
>> raj.khem@gmail.com]
>> -=-=-=-=-=-=-=-=-=-=-=-
>>
>>

[-- Attachment #2: Type: text/html, Size: 8708 bytes --]

Re: [yocto] [meta-lts-mixins][dunfell/go PATCH 1/4] Initial commit: add license, readme and layer config.

[Alexander Kanavin]

[-- Attachment #1: Type: text/plain, Size: 666 bytes --]

On Thu, 27 Jan 2022 at 21:06, Denys Dmytriyenko <denis@denix.org> wrote:

> On Thu, Jan 27, 2022 at 06:07:06PM +0100, Alexander Kanavin wrote:
> > A question specifically to Denys, how can I actually get this into the
> > mixin repo, and have commit rights to the branch? We've tested this quite
> > well in private, and there are further enhancements coming up.
>
> Michael,
>
> Would it be possible to create 2 additional branches in the
> meta-lts-mixins
> repository at https://git.yoctoproject.org/meta-lts-mixins/ called
> "dunfell/go" and also "dunfell/docker" and give Alex push rights to them?
>
> Please let us know, thanks a lot!
>

Ping, please :)

Alex

[-- Attachment #2: Type: text/html, Size: 1232 bytes --]

Re: [yocto] [meta-lts-mixins][dunfell/go PATCH 1/4] Initial commit: add license, readme and layer config.

[Michael Halstead]

[-- Attachment #1: Type: text/plain, Size: 919 bytes --]

Thank you for the ping. These branches are ready for you.

On Tue, Feb 1, 2022 at 6:23 AM Alexander Kanavin <alex.kanavin@gmail.com>
wrote:

> On Thu, 27 Jan 2022 at 21:06, Denys Dmytriyenko <denis@denix.org> wrote:
>
>> On Thu, Jan 27, 2022 at 06:07:06PM +0100, Alexander Kanavin wrote:
>> > A question specifically to Denys, how can I actually get this into the
>> > mixin repo, and have commit rights to the branch? We've tested this
>> quite
>> > well in private, and there are further enhancements coming up.
>>
>> Michael,
>>
>> Would it be possible to create 2 additional branches in the
>> meta-lts-mixins
>> repository at https://git.yoctoproject.org/meta-lts-mixins/ called
>> "dunfell/go" and also "dunfell/docker" and give Alex push rights to them?
>>
>> Please let us know, thanks a lot!
>>
>
> Ping, please :)
>
> Alex
>


-- 
Michael Halstead
Linux Foundation / Yocto Project
Systems Operations Engineer

[-- Attachment #2: Type: text/html, Size: 1873 bytes --]

Re: [yocto] [meta-lts-mixins][dunfell/go PATCH 1/4] Initial commit: add license, readme and layer config.

[Alexander Kanavin]

[-- Attachment #1: Type: text/plain, Size: 1326 bytes --]

Thanks Michael!
Adrian, the branches are now available:

https://git.yoctoproject.org/meta-lts-mixins

so I'm ready to take any patches you would like to have there, pls send
them via this mailing list. Otherwise I'll get the branches updated to
latest component versions.

Alex

On Thu, 3 Feb 2022 at 00:50, Michael Halstead <mhalstead@linuxfoundation.org>
wrote:

> Thank you for the ping. These branches are ready for you.
>
> On Tue, Feb 1, 2022 at 6:23 AM Alexander Kanavin <alex.kanavin@gmail.com>
> wrote:
>
>> On Thu, 27 Jan 2022 at 21:06, Denys Dmytriyenko <denis@denix.org> wrote:
>>
>>> On Thu, Jan 27, 2022 at 06:07:06PM +0100, Alexander Kanavin wrote:
>>> > A question specifically to Denys, how can I actually get this into the
>>> > mixin repo, and have commit rights to the branch? We've tested this
>>> quite
>>> > well in private, and there are further enhancements coming up.
>>>
>>> Michael,
>>>
>>> Would it be possible to create 2 additional branches in the
>>> meta-lts-mixins
>>> repository at https://git.yoctoproject.org/meta-lts-mixins/ called
>>> "dunfell/go" and also "dunfell/docker" and give Alex push rights to them?
>>>
>>> Please let us know, thanks a lot!
>>>
>>
>> Ping, please :)
>>
>> Alex
>>
>
>
> --
> Michael Halstead
> Linux Foundation / Yocto Project
> Systems Operations Engineer
>

[-- Attachment #2: Type: text/html, Size: 2689 bytes --]

Re: [yocto] [meta-lts-mixins][dunfell/go PATCH 1/4] Initial commit: add license, readme and layer config.

[Alexander Kanavin]

[-- Attachment #1: Type: text/plain, Size: 671 bytes --]

On Thu, 27 Jan 2022 at 15:48, Konrad Weihmann <kweihmann@outlook.com> wrote:

> > +GOVERSION ?= "1.17%"
> > +PREFERRED_PROVIDER_go-native = "go-binary-native"
>
> Just out of curiosity: I thought the agreement was that neither
> PREFERRED_PROVIDER_* nor recipe/provider specific settings should be
> part of a layer.conf
> PREFERRED_PROVIDER_go-native as a hard assignment might be troublesome
> in some setups (mainly depending on what order bblayers.conf actually has)
>

Yes, but this way it 'just works'. I do not think writing complicated
instructions in README for what needs to be in local.conf or distro config
is a better alternative. Suggestions welcome.

Alex

[-- Attachment #2: Type: text/html, Size: 1140 bytes --]

Re: [yocto] [meta-lts-mixins][dunfell/go PATCH 1/4] Initial commit: add license, readme and layer config.

[Konrad Weihmann]

On 27.01.22 15:43, Alexander Kanavin wrote:
> Reviewed-by: Martin Kaistra <martin.kaistra@linutronix.de>
> Signed-off-by: Alexander Kanavin <alex@linutronix.de>
> ---
>   COPYING.MIT     | 17 +++++++++++++++++
>   README          | 23 +++++++++++++++++++++++
>   conf/layer.conf | 19 +++++++++++++++++++
>   3 files changed, 59 insertions(+)
>   create mode 100644 COPYING.MIT
>   create mode 100644 README
>   create mode 100644 conf/layer.conf
> 
> diff --git a/COPYING.MIT b/COPYING.MIT
> new file mode 100644
> index 0000000..fb950dc
> --- /dev/null
> +++ b/COPYING.MIT
> @@ -0,0 +1,17 @@
> +Permission is hereby granted, free of charge, to any person obtaining a copy
> +of this software and associated documentation files (the "Software"), to deal
> +in the Software without restriction, including without limitation the rights
> +to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
> +copies of the Software, and to permit persons to whom the Software is
> +furnished to do so, subject to the following conditions:
> +
> +The above copyright notice and this permission notice shall be included in
> +all copies or substantial portions of the Software.
> +
> +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
> +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
> +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
> +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
> +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
> +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
> +THE SOFTWARE.
> diff --git a/README b/README
> new file mode 100644
> index 0000000..5b22b72
> --- /dev/null
> +++ b/README
> @@ -0,0 +1,23 @@
> +"Mixin" layer for adding latest Go toolchain versions into the Yocto Project LTS.
> +
> +At the time Dunfell was released in April 2020, Go 1.14 was the latest version
> +and officially Dunfell supports only that. This thin special-purpose mixin
> +layer is meant to address this issue by backporting Go recipes from the master
> +branch of openembedded-core.
> +
> +You can see what Go versions are provided by listing recipes-devtools/ content.
> +
> +Including the layer automatically picks up the latest Go version; different versions
> +need to be set explicitly by adding the following line to your distro config
> +or local.conf:
> +
> +GOVERSION = "1.16%"
> +
> +Please note: enabling these newer Go versions makes docker from dunfell branch
> +of meta-virtualization unbuildable as it is too old. If you need a working docker
> +recipe, you can use the supplementary 'dunfell/docker' layer from this meta-lts-mixin
> +repository.
> +
> +
> +Maintainers:
> +Alexander Kanavin <alex@linutronix.de>
> diff --git a/conf/layer.conf b/conf/layer.conf
> new file mode 100644
> index 0000000..5f74224
> --- /dev/null
> +++ b/conf/layer.conf
> @@ -0,0 +1,19 @@
> +# We have a conf and classes directory, append to BBPATH
> +BBPATH .= ":${LAYERDIR}"
> +
> +# We have a recipes directory, add to BBFILES
> +BBFILES += "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend"
> +
> +BBFILE_COLLECTIONS += "lts-go-mixin"
> +BBFILE_PATTERN_lts-go-mixin := "^${LAYERDIR}/"
> +BBFILE_PRIORITY_lts-go-mixin = "6"
> +
> +LAYERSERIES_COMPAT_lts-go-mixin = "dunfell"
> +
> +LAYERDEPENDS_lts-go-mixin = " \
> +    core \
> +"
> +
> +GOVERSION ?= "1.17%"
> +PREFERRED_PROVIDER_go-native = "go-binary-native"

Just out of curiosity: I thought the agreement was that neither 
PREFERRED_PROVIDER_* nor recipe/provider specific settings should be 
part of a layer.conf
PREFERRED_PROVIDER_go-native as a hard assignment might be troublesome 
in some setups (mainly depending on what order bblayers.conf actually has)

> +
> 
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#55990): https://lists.yoctoproject.org/g/yocto/message/55990
> Mute This Topic: https://lists.yoctoproject.org/mt/88722205/3647476
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [kweihmann@outlook.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>