* [meta-kde][PATCH 1/3] packagegroup-kde-apps: remove multiline comment @ 2013-03-07 9:50 Koen Kooi 2013-03-07 9:50 ` [meta-kde][PATCH 2/3] ark, gwenview: fix RDEPENDS Koen Kooi 2013-03-07 9:50 ` [meta-kde][PATCH 3/3] README: update contributor list Koen Kooi 0 siblings, 2 replies; 23+ messages in thread From: Koen Kooi @ 2013-03-07 9:50 UTC (permalink / raw) To: openembedded-devel; +Cc: Koen Kooi ERROR: There is a confusing multiline, partially commented expression on line 12 of file /build/setup-scripts/sources/meta-kde/recipes-packagegroups/packagegroup-kde-apps.bb (). Please clarify whether this is all a comment or should be parsed. ERROR: Unable to parse /build/setup-scripts/sources/meta-kde/recipes-packagegroups/packagegroup-kde-apps.bb: Exited with "1" | ETA: --:--:-- ERROR: Command execution failed: Exited with 1 Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> --- recipes-packagegroups/packagegroup-kde-apps.bb | 11 ----------- 1 file changed, 11 deletions(-) diff --git a/recipes-packagegroups/packagegroup-kde-apps.bb b/recipes-packagegroups/packagegroup-kde-apps.bb index 4258c4f..3cac437 100644 --- a/recipes-packagegroups/packagegroup-kde-apps.bb +++ b/recipes-packagegroups/packagegroup-kde-apps.bb @@ -1,14 +1,3 @@ -#Defect with Qt<4.8.2 -#calligra \ -#calligra-braindump \ -#calligra-flow \ -#calligra-karbon \ -#calligra-kexi \ -#calligra-krita \ -#calligra-plan \ -#calligra-sheets \ -#calligra-stage \ -#calligra-words \ DESCRIPTION = "KDE packagegroup for applications" LICENSE = "MIT" LIC_FILES_CHKSUM = "file://${COREBASE}/LICENSE;md5=3f40d7994397109285ec7b81fdeb3b58" -- 1.8.1.4 ^ permalink raw reply related [flat|nested] 23+ messages in thread
* [meta-kde][PATCH 2/3] ark, gwenview: fix RDEPENDS 2013-03-07 9:50 [meta-kde][PATCH 1/3] packagegroup-kde-apps: remove multiline comment Koen Kooi @ 2013-03-07 9:50 ` Koen Kooi 2013-03-07 9:50 ` [meta-kde][PATCH 3/3] README: update contributor list Koen Kooi 1 sibling, 0 replies; 23+ messages in thread From: Koen Kooi @ 2013-03-07 9:50 UTC (permalink / raw) To: openembedded-devel; +Cc: Koen Kooi ERROR: QA Issue: /build/setup-scripts/sources/meta-kde/recipes-kde-apps/gwenview_git.bb: Variable RDEPENDS is set as not being package specific, please fix this. | ETA: --:--:-- ERROR: QA Issue: /build/setup-scripts/sources/meta-kde/recipes-kde-apps/ark_git.bb: Variable RDEPENDS is set as not being package specific, please fix this. Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> --- recipes-kde-apps/ark_git.bb | 2 +- recipes-kde-apps/gwenview_git.bb | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/recipes-kde-apps/ark_git.bb b/recipes-kde-apps/ark_git.bb index f33d8b1..844bc3f 100644 --- a/recipes-kde-apps/ark_git.bb +++ b/recipes-kde-apps/ark_git.bb @@ -14,7 +14,7 @@ S = "${WORKDIR}/git" inherit kde_cmake kde_rdepends kde_without_docs # for videos? -RDEPENDS = "libqtphonon4" +RDEPENDS_${PN} = "libqtphonon4" FILES_${PN} += "\ ${libdir}/kde4/*.so \ diff --git a/recipes-kde-apps/gwenview_git.bb b/recipes-kde-apps/gwenview_git.bb index 0fb85d8..1068aba 100644 --- a/recipes-kde-apps/gwenview_git.bb +++ b/recipes-kde-apps/gwenview_git.bb @@ -15,7 +15,7 @@ S = "${WORKDIR}/git" inherit kde_cmake kde_rdepends kde_without_docs # for videos? -RDEPENDS = "libqtphonon4" +RDEPENDS_${PN} = "libqtphonon4" FILES_${PN} += "${datadir} \ ${libdir}/kde4/*.so" -- 1.8.1.4 ^ permalink raw reply related [flat|nested] 23+ messages in thread
* [meta-kde][PATCH 3/3] README: update contributor list 2013-03-07 9:50 [meta-kde][PATCH 1/3] packagegroup-kde-apps: remove multiline comment Koen Kooi 2013-03-07 9:50 ` [meta-kde][PATCH 2/3] ark, gwenview: fix RDEPENDS Koen Kooi @ 2013-03-07 9:50 ` Koen Kooi 2013-03-07 12:09 ` Samuel Stirtzel 1 sibling, 1 reply; 23+ messages in thread From: Koen Kooi @ 2013-03-07 9:50 UTC (permalink / raw) To: openembedded-devel; +Cc: Koen Kooi Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> --- README | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README b/README index 0635e10..cab1e21 100644 --- a/README +++ b/README @@ -10,7 +10,7 @@ Samuel Stirtzel <s.stirtzel@googlemail.com> Contributors: Copyright 2012 - Kai Kang Copyright 2013 - Khem Raj -Copyright 2012 - Koen Kooi +Copyright 2012, 2013 - Koen Kooi Copyright 2012 - Robert Yang Copyright 2011, 2012 - Samuel Stirtzel -- 1.8.1.4 ^ permalink raw reply related [flat|nested] 23+ messages in thread
* Re: [meta-kde][PATCH 3/3] README: update contributor list 2013-03-07 9:50 ` [meta-kde][PATCH 3/3] README: update contributor list Koen Kooi @ 2013-03-07 12:09 ` Samuel Stirtzel 2013-03-07 13:04 ` Martin Jansa ` (2 more replies) 0 siblings, 3 replies; 23+ messages in thread From: Samuel Stirtzel @ 2013-03-07 12:09 UTC (permalink / raw) To: Koen Kooi; +Cc: openembedded-devel 2013/3/7 Koen Kooi <koen@dominion.thruhere.net>: > Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> > --- > README | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/README b/README > index 0635e10..cab1e21 100644 > --- a/README > +++ b/README > @@ -10,7 +10,7 @@ Samuel Stirtzel <s.stirtzel@googlemail.com> > Contributors: > Copyright 2012 - Kai Kang > Copyright 2013 - Khem Raj > -Copyright 2012 - Koen Kooi > +Copyright 2012, 2013 - Koen Kooi > Copyright 2012 - Robert Yang > Copyright 2011, 2012 - Samuel Stirtzel > > -- > 1.8.1.4 > Thanks for your patches, I applied them all. Unrelated to your patches: There are some upcoming changes, but they don't fit into yocto 1.4 (assumed that yocto is the orientation point for third-party OE-layer releases). So there will be a yocto-1.4 branch in advance and the development will continue on master. Hopefully meta-angstrom + meta-oe + oe-core + <bsp-layer> is a supported use case in yocto ... -- Regards Samuel ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [meta-kde][PATCH 3/3] README: update contributor list 2013-03-07 12:09 ` Samuel Stirtzel @ 2013-03-07 13:04 ` Martin Jansa 2013-03-07 14:03 ` Koen Kooi 2013-03-07 13:10 ` Paul Eggleton 2013-03-07 15:05 ` Martin Jansa 2 siblings, 1 reply; 23+ messages in thread From: Martin Jansa @ 2013-03-07 13:04 UTC (permalink / raw) To: openembedded-devel; +Cc: Koen Kooi [-- Attachment #1: Type: text/plain, Size: 1638 bytes --] On Thu, Mar 07, 2013 at 01:09:38PM +0100, Samuel Stirtzel wrote: > 2013/3/7 Koen Kooi <koen@dominion.thruhere.net>: > > Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> > > --- > > README | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff --git a/README b/README > > index 0635e10..cab1e21 100644 > > --- a/README > > +++ b/README > > @@ -10,7 +10,7 @@ Samuel Stirtzel <s.stirtzel@googlemail.com> > > Contributors: > > Copyright 2012 - Kai Kang > > Copyright 2013 - Khem Raj > > -Copyright 2012 - Koen Kooi > > +Copyright 2012, 2013 - Koen Kooi > > Copyright 2012 - Robert Yang > > Copyright 2011, 2012 - Samuel Stirtzel > > > > -- > > 1.8.1.4 > > > > Thanks for your patches, > I applied them all. > > > Unrelated to your patches: > There are some upcoming changes, but they don't fit into yocto 1.4 > (assumed that yocto is the orientation point for third-party OE-layer > releases). > So there will be a yocto-1.4 branch in advance and the development > will continue on master. It would be nice to know yocto-1.4 release name in advance and name it the same as branch in oe-core/meta-oe will be (denzil, danny, ...), but I guess it can be renamed later. > Hopefully meta-angstrom + meta-oe + oe-core + <bsp-layer> is a > supported use case in yocto ... > > -- > Regards > Samuel > > _______________________________________________ > Openembedded-devel mailing list > Openembedded-devel@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel -- Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 205 bytes --] ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [meta-kde][PATCH 3/3] README: update contributor list 2013-03-07 13:04 ` Martin Jansa @ 2013-03-07 14:03 ` Koen Kooi 2013-03-07 14:35 ` Paul Eggleton 2013-03-07 15:30 ` Richard Purdie 0 siblings, 2 replies; 23+ messages in thread From: Koen Kooi @ 2013-03-07 14:03 UTC (permalink / raw) To: Martin Jansa; +Cc: openembedded-devel Op 7 mrt. 2013, om 14:04 heeft Martin Jansa <martin.jansa@gmail.com> het volgende geschreven: > On Thu, Mar 07, 2013 at 01:09:38PM +0100, Samuel Stirtzel wrote: >> 2013/3/7 Koen Kooi <koen@dominion.thruhere.net>: >>> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> >>> --- >>> README | 2 +- >>> 1 file changed, 1 insertion(+), 1 deletion(-) >>> >>> diff --git a/README b/README >>> index 0635e10..cab1e21 100644 >>> --- a/README >>> +++ b/README >>> @@ -10,7 +10,7 @@ Samuel Stirtzel <s.stirtzel@googlemail.com> >>> Contributors: >>> Copyright 2012 - Kai Kang >>> Copyright 2013 - Khem Raj >>> -Copyright 2012 - Koen Kooi >>> +Copyright 2012, 2013 - Koen Kooi >>> Copyright 2012 - Robert Yang >>> Copyright 2011, 2012 - Samuel Stirtzel >>> >>> -- >>> 1.8.1.4 >>> >> >> Thanks for your patches, >> I applied them all. >> >> >> Unrelated to your patches: >> There are some upcoming changes, but they don't fit into yocto 1.4 >> (assumed that yocto is the orientation point for third-party OE-layer >> releases). >> So there will be a yocto-1.4 branch in advance and the development >> will continue on master. > > It would be nice to know yocto-1.4 release name in advance and name it > the same as branch in oe-core/meta-oe will be (denzil, danny, ...), but > I guess it can be renamed later. For angstrom I'm going to use 'yocto-1.4' in the branch name, I have trouble remembering which names maps to which release. And the Yocto compliance program talks about 1.3, .14 etc, not about codenames. ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [meta-kde][PATCH 3/3] README: update contributor list 2013-03-07 14:03 ` Koen Kooi @ 2013-03-07 14:35 ` Paul Eggleton 2013-03-07 14:41 ` Otavio Salvador 2013-03-07 15:30 ` Richard Purdie 1 sibling, 1 reply; 23+ messages in thread From: Paul Eggleton @ 2013-03-07 14:35 UTC (permalink / raw) To: Koen Kooi; +Cc: openembedded-devel, Martin Jansa On Thursday 07 March 2013 15:03:17 Koen Kooi wrote: > Op 7 mrt. 2013, om 14:04 heeft Martin Jansa <martin.jansa@gmail.com> het > volgende geschreven: > > It would be nice to know yocto-1.4 release name in advance and name it > > the same as branch in oe-core/meta-oe will be (denzil, danny, ...), but > > I guess it can be renamed later. > > For angstrom I'm going to use 'yocto-1.4' in the branch name, I have trouble > remembering which names maps to which release. And the Yocto compliance > program talks about 1.3, .14 etc, not about codenames. Wouldn't it be worth us trying to standardise rather than all doing our own thing and users having to figure out what matches up between different layers? If others feel the same as you, then maybe we should all be using that schema. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [meta-kde][PATCH 3/3] README: update contributor list 2013-03-07 14:35 ` Paul Eggleton @ 2013-03-07 14:41 ` Otavio Salvador 2013-03-07 14:50 ` Philip Balister 2013-03-07 14:52 ` Martin Jansa 0 siblings, 2 replies; 23+ messages in thread From: Otavio Salvador @ 2013-03-07 14:41 UTC (permalink / raw) To: OpenEmbedded Devel List; +Cc: Koen Kooi, Martin Jansa On Thu, Mar 7, 2013 at 11:35 AM, Paul Eggleton <paul.eggleton@linux.intel.com> wrote: > On Thursday 07 March 2013 15:03:17 Koen Kooi wrote: >> Op 7 mrt. 2013, om 14:04 heeft Martin Jansa <martin.jansa@gmail.com> het >> volgende geschreven: >> > It would be nice to know yocto-1.4 release name in advance and name it >> > the same as branch in oe-core/meta-oe will be (denzil, danny, ...), but >> > I guess it can be renamed later. >> >> For angstrom I'm going to use 'yocto-1.4' in the branch name, I have trouble >> remembering which names maps to which release. And the Yocto compliance >> program talks about 1.3, .14 etc, not about codenames. > > Wouldn't it be worth us trying to standardise rather than all doing our own > thing and users having to figure out what matches up between different layers? > If others feel the same as you, then maybe we should all be using that schema. Or we use a codename or we don't. For me, codenames work fine but for users it is sometimes confusing as the website and marketing people talk about Yocto 1.3 or 1.4 while the involved people talk about codenames. So I find myself explaining it over and over again. -- Otavio Salvador O.S. Systems E-mail: otavio@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [meta-kde][PATCH 3/3] README: update contributor list 2013-03-07 14:41 ` Otavio Salvador @ 2013-03-07 14:50 ` Philip Balister 2013-03-07 15:05 ` Burton, Ross 2013-03-07 15:41 ` Paul Eggleton 2013-03-07 14:52 ` Martin Jansa 1 sibling, 2 replies; 23+ messages in thread From: Philip Balister @ 2013-03-07 14:50 UTC (permalink / raw) To: openembedded-devel; +Cc: Koen Kooi, Martin Jansa, Otavio Salvador On 03/07/2013 09:41 AM, Otavio Salvador wrote: > On Thu, Mar 7, 2013 at 11:35 AM, Paul Eggleton > <paul.eggleton@linux.intel.com> wrote: >> On Thursday 07 March 2013 15:03:17 Koen Kooi wrote: >>> Op 7 mrt. 2013, om 14:04 heeft Martin Jansa <martin.jansa@gmail.com> het >>> volgende geschreven: >>>> It would be nice to know yocto-1.4 release name in advance and name it >>>> the same as branch in oe-core/meta-oe will be (denzil, danny, ...), but >>>> I guess it can be renamed later. >>> >>> For angstrom I'm going to use 'yocto-1.4' in the branch name, I have trouble >>> remembering which names maps to which release. And the Yocto compliance >>> program talks about 1.3, .14 etc, not about codenames. >> >> Wouldn't it be worth us trying to standardise rather than all doing our own >> thing and users having to figure out what matches up between different layers? >> If others feel the same as you, then maybe we should all be using that schema. > > Or we use a codename or we don't. > > For me, codenames work fine but for users it is sometimes confusing as > the website and marketing people talk about Yocto 1.3 or 1.4 while the > involved people talk about codenames. So I find myself explaining it > over and over again. > Add me to the list of people that find codenames confusing. I can't reliably list releases in order by name. Philip ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [meta-kde][PATCH 3/3] README: update contributor list 2013-03-07 14:50 ` Philip Balister @ 2013-03-07 15:05 ` Burton, Ross 2013-03-07 15:15 ` Burton, Ross 2013-03-07 15:41 ` Paul Eggleton 1 sibling, 1 reply; 23+ messages in thread From: Burton, Ross @ 2013-03-07 15:05 UTC (permalink / raw) To: openembedded-devel; +Cc: Koen Kooi, Martin Jansa, Otavio Salvador On 7 March 2013 14:50, Philip Balister <philip@balister.org> wrote: >> For me, codenames work fine but for users it is sometimes confusing as >> the website and marketing people talk about Yocto 1.3 or 1.4 while the >> involved people talk about codenames. So I find myself explaining it >> over and over again. > > Add me to the list of people that find codenames confusing. I can't > reliably list releases in order by name. We really need a table on the wiki page listing all of them - I can easily remember the current/previous/next names but after that I don't remember them. Ross ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [meta-kde][PATCH 3/3] README: update contributor list 2013-03-07 15:05 ` Burton, Ross @ 2013-03-07 15:15 ` Burton, Ross 2013-03-07 15:18 ` Koen Kooi 0 siblings, 1 reply; 23+ messages in thread From: Burton, Ross @ 2013-03-07 15:15 UTC (permalink / raw) To: openembedded-devel; +Cc: Koen Kooi, Martin Jansa, Otavio Salvador On 7 March 2013 15:05, Burton, Ross <ross.burton@intel.com> wrote: > We really need a table on the wiki page listing all of them - I can > easily remember the current/previous/next names but after that I don't > remember them. JFDI. https://wiki.yoctoproject.org/wiki/Releases Only goes back to Poky 4/oe-core 0.9 at the moment, I'll fill in the pre-Yocto names later. Ross ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [meta-kde][PATCH 3/3] README: update contributor list 2013-03-07 15:15 ` Burton, Ross @ 2013-03-07 15:18 ` Koen Kooi 2013-03-07 15:24 ` Richard Purdie 0 siblings, 1 reply; 23+ messages in thread From: Koen Kooi @ 2013-03-07 15:18 UTC (permalink / raw) To: Burton, Ross; +Cc: openembedded-devel, Otavio Salvador, Martin Jansa Op 7 mrt. 2013, om 16:15 heeft "Burton, Ross" <ross.burton@intel.com> het volgende geschreven: > On 7 March 2013 15:05, Burton, Ross <ross.burton@intel.com> wrote: >> We really need a table on the wiki page listing all of them - I can >> easily remember the current/previous/next names but after that I don't >> remember them. > > JFDI. > > https://wiki.yoctoproject.org/wiki/Releases > > Only goes back to Poky 4/oe-core 0.9 at the moment, I'll fill in the > pre-Yocto names later. I asked this earlier in jest, but it requires a real response in this day and age: Are those yocto project releases or poky releases? I get the feeling the codenames are only for poky releases, so I strongly prefer using the numbers releases in branch names. ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [meta-kde][PATCH 3/3] README: update contributor list 2013-03-07 15:18 ` Koen Kooi @ 2013-03-07 15:24 ` Richard Purdie 0 siblings, 0 replies; 23+ messages in thread From: Richard Purdie @ 2013-03-07 15:24 UTC (permalink / raw) To: openembedded-devel; +Cc: Otavio Salvador, Martin Jansa On Thu, 2013-03-07 at 16:18 +0100, Koen Kooi wrote: > Op 7 mrt. 2013, om 16:15 heeft "Burton, Ross" <ross.burton@intel.com> het volgende geschreven: > > > On 7 March 2013 15:05, Burton, Ross <ross.burton@intel.com> wrote: > >> We really need a table on the wiki page listing all of them - I can > >> easily remember the current/previous/next names but after that I don't > >> remember them. > > > > JFDI. > > > > https://wiki.yoctoproject.org/wiki/Releases > > > > Only goes back to Poky 4/oe-core 0.9 at the moment, I'll fill in the > > pre-Yocto names later. > > I asked this earlier in jest, but it requires a real response in this day and age: > > Are those yocto project releases or poky releases? > > I get the feeling the codenames are only for poky releases, so I > strongly prefer using the numbers releases in branch names. They're stable release series codenames use by the Yocto Project, OpenEmbedded Core, Poky and anyone else who wishes to. Cheers, Richard ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [meta-kde][PATCH 3/3] README: update contributor list 2013-03-07 14:50 ` Philip Balister 2013-03-07 15:05 ` Burton, Ross @ 2013-03-07 15:41 ` Paul Eggleton 2013-03-11 12:34 ` Peter A. Bigot 1 sibling, 1 reply; 23+ messages in thread From: Paul Eggleton @ 2013-03-07 15:41 UTC (permalink / raw) To: openembedded-devel; +Cc: Koen Kooi, Martin Jansa, Otavio Salvador On Thursday 07 March 2013 09:50:21 Philip Balister wrote: > On 03/07/2013 09:41 AM, Otavio Salvador wrote: > > On Thu, Mar 7, 2013 at 11:35 AM, Paul Eggleton > > > > <paul.eggleton@linux.intel.com> wrote: > >> On Thursday 07 March 2013 15:03:17 Koen Kooi wrote: > >>> Op 7 mrt. 2013, om 14:04 heeft Martin Jansa <martin.jansa@gmail.com> het > >>> > >>> volgende geschreven: > >>>> It would be nice to know yocto-1.4 release name in advance and name it > >>>> the same as branch in oe-core/meta-oe will be (denzil, danny, ...), but > >>>> I guess it can be renamed later. > >>> > >>> For angstrom I'm going to use 'yocto-1.4' in the branch name, I have > >>> trouble remembering which names maps to which release. And the Yocto > >>> compliance program talks about 1.3, .14 etc, not about codenames. > >> > >> Wouldn't it be worth us trying to standardise rather than all doing our > >> own > >> thing and users having to figure out what matches up between different > >> layers? If others feel the same as you, then maybe we should all be > >> using that schema.> > > Or we use a codename or we don't. > > > > For me, codenames work fine but for users it is sometimes confusing as > > the website and marketing people talk about Yocto 1.3 or 1.4 while the > > involved people talk about codenames. So I find myself explaining it > > over and over again. > > Add me to the list of people that find codenames confusing. I can't > reliably list releases in order by name. FWIW, in the layer index web app against each branch I have a field for a short description (e.g. denzil could have something like "old stable" or whatever is helpful to explain it to people) and a sort order so that they can be sorted correctly where listed. That doesn't take away the need to resolve this issue of branch names across layers, but it may help users to understand what these codenames mean if they continue to be used, at least when they see them in the layer index at least. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [meta-kde][PATCH 3/3] README: update contributor list 2013-03-07 15:41 ` Paul Eggleton @ 2013-03-11 12:34 ` Peter A. Bigot 0 siblings, 0 replies; 23+ messages in thread From: Peter A. Bigot @ 2013-03-11 12:34 UTC (permalink / raw) To: openembedded-devel On 03/07/2013 09:41 AM, Paul Eggleton wrote: > On Thursday 07 March 2013 09:50:21 Philip Balister wrote: >> On 03/07/2013 09:41 AM, Otavio Salvador wrote: >>> On Thu, Mar 7, 2013 at 11:35 AM, Paul Eggleton >>> >>> <paul.eggleton@linux.intel.com> wrote: >>>> On Thursday 07 March 2013 15:03:17 Koen Kooi wrote: >>>>> Op 7 mrt. 2013, om 14:04 heeft Martin Jansa <martin.jansa@gmail.com> het >>>>> >>>>> volgende geschreven: >>>>>> It would be nice to know yocto-1.4 release name in advance and name it >>>>>> the same as branch in oe-core/meta-oe will be (denzil, danny, ...), but >>>>>> I guess it can be renamed later. >>>>> For angstrom I'm going to use 'yocto-1.4' in the branch name, I have >>>>> trouble remembering which names maps to which release. And the Yocto >>>>> compliance program talks about 1.3, .14 etc, not about codenames. >>>> Wouldn't it be worth us trying to standardise rather than all doing our >>>> own >>>> thing and users having to figure out what matches up between different >>>> layers? If others feel the same as you, then maybe we should all be >>>> using that schema.> >>> Or we use a codename or we don't. >>> >>> For me, codenames work fine but for users it is sometimes confusing as >>> the website and marketing people talk about Yocto 1.3 or 1.4 while the >>> involved people talk about codenames. So I find myself explaining it >>> over and over again. >> Add me to the list of people that find codenames confusing. I can't >> reliably list releases in order by name. > FWIW, in the layer index web app against each branch I have a field for a short > description (e.g. denzil could have something like "old stable" or whatever is > helpful to explain it to people) and a sort order so that they can be sorted > correctly where listed. > > That doesn't take away the need to resolve this issue of branch names across > layers, but it may help users to understand what these codenames mean if they > continue to be used, at least when they see them in the layer index at least. A comment on that from up here in the peanut gallery: I don't personally find codenames valuable, but if they're used it would be nice if they were selected using a policy that allowed at least their relative order to be determined by inspection. That danny=1.3 sorts lexicographically before denzil=1.2 is confusing. Peter ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [meta-kde][PATCH 3/3] README: update contributor list 2013-03-07 14:41 ` Otavio Salvador 2013-03-07 14:50 ` Philip Balister @ 2013-03-07 14:52 ` Martin Jansa 1 sibling, 0 replies; 23+ messages in thread From: Martin Jansa @ 2013-03-07 14:52 UTC (permalink / raw) To: Otavio Salvador; +Cc: Koen Kooi, OpenEmbedded Devel List [-- Attachment #1: Type: text/plain, Size: 1829 bytes --] On Thu, Mar 07, 2013 at 11:41:07AM -0300, Otavio Salvador wrote: > On Thu, Mar 7, 2013 at 11:35 AM, Paul Eggleton > <paul.eggleton@linux.intel.com> wrote: > > On Thursday 07 March 2013 15:03:17 Koen Kooi wrote: > >> Op 7 mrt. 2013, om 14:04 heeft Martin Jansa <martin.jansa@gmail.com> het > >> volgende geschreven: > >> > It would be nice to know yocto-1.4 release name in advance and name it > >> > the same as branch in oe-core/meta-oe will be (denzil, danny, ...), but > >> > I guess it can be renamed later. > >> > >> For angstrom I'm going to use 'yocto-1.4' in the branch name, I have trouble > >> remembering which names maps to which release. And the Yocto compliance > >> program talks about 1.3, .14 etc, not about codenames. > > > > Wouldn't it be worth us trying to standardise rather than all doing our own > > thing and users having to figure out what matches up between different layers? > > If others feel the same as you, then maybe we should all be using that schema. > > Or we use a codename or we don't. > > For me, codenames work fine but for users it is sometimes confusing as > the website and marketing people talk about Yocto 1.3 or 1.4 while the > involved people talk about codenames. So I find myself explaining it > over and over again. Yes I usually need to use both names, because some people want to hear "Yocto". But "Yocto 1.3" alone sometimes does not work in sentences like "Update oe-core to latest revision in danny branch (Yocto 1.3)" "Update bitbake to latest revision in 1.16 branch which is compatible with danny branches (Yocto 1.3)" So I agree it's confusing, like in this pull-request https://github.com/openwebos/build-webos/pull/25 Yes, I always forget to add "Project" :/. -- Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 205 bytes --] ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [meta-kde][PATCH 3/3] README: update contributor list 2013-03-07 14:03 ` Koen Kooi 2013-03-07 14:35 ` Paul Eggleton @ 2013-03-07 15:30 ` Richard Purdie 1 sibling, 0 replies; 23+ messages in thread From: Richard Purdie @ 2013-03-07 15:30 UTC (permalink / raw) To: openembedded-devel; +Cc: Martin Jansa On Thu, 2013-03-07 at 15:03 +0100, Koen Kooi wrote: > Op 7 mrt. 2013, om 14:04 heeft Martin Jansa <martin.jansa@gmail.com> het volgende geschreven: > > > On Thu, Mar 07, 2013 at 01:09:38PM +0100, Samuel Stirtzel wrote: > >> 2013/3/7 Koen Kooi <koen@dominion.thruhere.net>: > >>> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> > >>> --- > >>> README | 2 +- > >>> 1 file changed, 1 insertion(+), 1 deletion(-) > >>> > >>> diff --git a/README b/README > >>> index 0635e10..cab1e21 100644 > >>> --- a/README > >>> +++ b/README > >>> @@ -10,7 +10,7 @@ Samuel Stirtzel <s.stirtzel@googlemail.com> > >>> Contributors: > >>> Copyright 2012 - Kai Kang > >>> Copyright 2013 - Khem Raj > >>> -Copyright 2012 - Koen Kooi > >>> +Copyright 2012, 2013 - Koen Kooi > >>> Copyright 2012 - Robert Yang > >>> Copyright 2011, 2012 - Samuel Stirtzel > >>> > >>> -- > >>> 1.8.1.4 > >>> > >> > >> Thanks for your patches, > >> I applied them all. > >> > >> > >> Unrelated to your patches: > >> There are some upcoming changes, but they don't fit into yocto 1.4 > >> (assumed that yocto is the orientation point for third-party OE-layer > >> releases). > >> So there will be a yocto-1.4 branch in advance and the development > >> will continue on master. > > > > It would be nice to know yocto-1.4 release name in advance and name it > > the same as branch in oe-core/meta-oe will be (denzil, danny, ...), but > > I guess it can be renamed later. > > For angstrom I'm going to use 'yocto-1.4' in the branch name, I have > trouble remembering which names maps to which release. And the Yocto > compliance program talks about 1.3, .14 etc, not about codenames. That is just going to cause even more confusion. That branch is for Angstrom 1.4, right? It was never intended to inflict any specific version onto any specific project which is why the names are versionless. We do need to show what is compatible with what hence the codenames. I've long since decided this is a topic there is no one right answer to though so we'll just have to live with where we are and make the most of it. I've sent out emails about this before too. If we need to know the name of the branch more in advance, that is straight forward to arrange, I just need to pick the next one. Cheers, Richard ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [meta-kde][PATCH 3/3] README: update contributor list 2013-03-07 12:09 ` Samuel Stirtzel 2013-03-07 13:04 ` Martin Jansa @ 2013-03-07 13:10 ` Paul Eggleton 2013-03-07 14:04 ` Samuel Stirtzel 2013-03-07 15:05 ` Martin Jansa 2 siblings, 1 reply; 23+ messages in thread From: Paul Eggleton @ 2013-03-07 13:10 UTC (permalink / raw) To: Samuel Stirtzel; +Cc: openembedded-devel On Thursday 07 March 2013 13:09:38 Samuel Stirtzel wrote: > Unrelated to your patches: > There are some upcoming changes, but they don't fit into yocto 1.4 > (assumed that yocto is the orientation point for third-party OE-layer > releases). > So there will be a yocto-1.4 branch in advance and the development > will continue on master. FYI, the layer index web interface I'm putting together [1] will understand certain branch names across all layers, and the convention so far has been to use the release names i.e. denzil, danny, etc. If you are able to follow this as well once the 1.4 codename has been announced then your branch will show up correctly in the new interface. Cheers, Paul [1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=3272 -- Paul Eggleton Intel Open Source Technology Centre ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [meta-kde][PATCH 3/3] README: update contributor list 2013-03-07 13:10 ` Paul Eggleton @ 2013-03-07 14:04 ` Samuel Stirtzel 0 siblings, 0 replies; 23+ messages in thread From: Samuel Stirtzel @ 2013-03-07 14:04 UTC (permalink / raw) To: Paul Eggleton; +Cc: openembedded-devel 2013/3/7 Paul Eggleton <paul.eggleton@linux.intel.com>: > On Thursday 07 March 2013 13:09:38 Samuel Stirtzel wrote: >> Unrelated to your patches: >> There are some upcoming changes, but they don't fit into yocto 1.4 >> (assumed that yocto is the orientation point for third-party OE-layer >> releases). >> So there will be a yocto-1.4 branch in advance and the development >> will continue on master. > > FYI, the layer index web interface I'm putting together [1] will understand > certain branch names across all layers, and the convention so far has been to > use the release names i.e. denzil, danny, etc. If you are able to follow this > as well once the 1.4 codename has been announced then your branch will show up > correctly in the new interface. > > Cheers, > Paul > > [1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=3272 > Good to know, so layers like meta-qt5 [1] for example will be found more easily. I will rename the branch after the codename has been announced, but yes it would be easier if the name could get announced long before the release. [1] https://github.com/meta-qt5/meta-qt5 -- Regards Samuel ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [meta-kde][PATCH 3/3] README: update contributor list 2013-03-07 12:09 ` Samuel Stirtzel 2013-03-07 13:04 ` Martin Jansa 2013-03-07 13:10 ` Paul Eggleton @ 2013-03-07 15:05 ` Martin Jansa 2013-03-07 15:20 ` Samuel Stirtzel 2 siblings, 1 reply; 23+ messages in thread From: Martin Jansa @ 2013-03-07 15:05 UTC (permalink / raw) To: openembedded-devel; +Cc: Koen Kooi [-- Attachment #1: Type: text/plain, Size: 945 bytes --] On Thu, Mar 07, 2013 at 01:09:38PM +0100, Samuel Stirtzel wrote: > 2013/3/7 Koen Kooi <koen@dominion.thruhere.net>: > > Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> > > --- > > README | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff --git a/README b/README > > index 0635e10..cab1e21 100644 > > --- a/README > > +++ b/README > > @@ -10,7 +10,7 @@ Samuel Stirtzel <s.stirtzel@googlemail.com> > > Contributors: > > Copyright 2012 - Kai Kang > > Copyright 2013 - Khem Raj > > -Copyright 2012 - Koen Kooi > > +Copyright 2012, 2013 - Koen Kooi > > Copyright 2012 - Robert Yang > > Copyright 2011, 2012 - Samuel Stirtzel > > > > -- > > 1.8.1.4 > > > > Thanks for your patches, > I applied them all. Can you update status on: http://patches.openembedded.org/bundle/jama/meta-kde/?archive=both To keep patchwork clean? -- Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 205 bytes --] ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [meta-kde][PATCH 3/3] README: update contributor list 2013-03-07 15:05 ` Martin Jansa @ 2013-03-07 15:20 ` Samuel Stirtzel 2013-03-07 15:56 ` Martin Jansa 0 siblings, 1 reply; 23+ messages in thread From: Samuel Stirtzel @ 2013-03-07 15:20 UTC (permalink / raw) To: openembedded-devel 2013/3/7 Martin Jansa <martin.jansa@gmail.com>: > On Thu, Mar 07, 2013 at 01:09:38PM +0100, Samuel Stirtzel wrote: >> 2013/3/7 Koen Kooi <koen@dominion.thruhere.net>: >> > Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> >> > --- >> > README | 2 +- >> > 1 file changed, 1 insertion(+), 1 deletion(-) >> > >> > diff --git a/README b/README >> > index 0635e10..cab1e21 100644 >> > --- a/README >> > +++ b/README >> > @@ -10,7 +10,7 @@ Samuel Stirtzel <s.stirtzel@googlemail.com> >> > Contributors: >> > Copyright 2012 - Kai Kang >> > Copyright 2013 - Khem Raj >> > -Copyright 2012 - Koen Kooi >> > +Copyright 2012, 2013 - Koen Kooi >> > Copyright 2012 - Robert Yang >> > Copyright 2011, 2012 - Samuel Stirtzel >> > >> > -- >> > 1.8.1.4 >> > >> >> Thanks for your patches, >> I applied them all. > > Can you update status on: > http://patches.openembedded.org/bundle/jama/meta-kde/?archive=both > > To keep patchwork clean? > I would, but unfortunately I have no Patchwork account. Also there seems to be no possibility to register a new account. -- Regards Samuel ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [meta-kde][PATCH 3/3] README: update contributor list 2013-03-07 15:20 ` Samuel Stirtzel @ 2013-03-07 15:56 ` Martin Jansa 2013-03-20 12:14 ` Samuel Stirtzel 0 siblings, 1 reply; 23+ messages in thread From: Martin Jansa @ 2013-03-07 15:56 UTC (permalink / raw) To: openembedded-devel [-- Attachment #1: Type: text/plain, Size: 1356 bytes --] On Thu, Mar 07, 2013 at 04:20:42PM +0100, Samuel Stirtzel wrote: > 2013/3/7 Martin Jansa <martin.jansa@gmail.com>: > > On Thu, Mar 07, 2013 at 01:09:38PM +0100, Samuel Stirtzel wrote: > >> 2013/3/7 Koen Kooi <koen@dominion.thruhere.net>: > >> > Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> > >> > --- > >> > README | 2 +- > >> > 1 file changed, 1 insertion(+), 1 deletion(-) > >> > > >> > diff --git a/README b/README > >> > index 0635e10..cab1e21 100644 > >> > --- a/README > >> > +++ b/README > >> > @@ -10,7 +10,7 @@ Samuel Stirtzel <s.stirtzel@googlemail.com> > >> > Contributors: > >> > Copyright 2012 - Kai Kang > >> > Copyright 2013 - Khem Raj > >> > -Copyright 2012 - Koen Kooi > >> > +Copyright 2012, 2013 - Koen Kooi > >> > Copyright 2012 - Robert Yang > >> > Copyright 2011, 2012 - Samuel Stirtzel > >> > > >> > -- > >> > 1.8.1.4 > >> > > >> > >> Thanks for your patches, > >> I applied them all. > > > > Can you update status on: > > http://patches.openembedded.org/bundle/jama/meta-kde/?archive=both > > > > To keep patchwork clean? > > > > I would, but unfortunately I have no Patchwork account. > Also there seems to be no possibility to register a new account. Adding khem to CC: I guess he can arrange account for you. -- Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 205 bytes --] ^ permalink raw reply [flat|nested] 23+ messages in thread
* Re: [meta-kde][PATCH 3/3] README: update contributor list 2013-03-07 15:56 ` Martin Jansa @ 2013-03-20 12:14 ` Samuel Stirtzel 0 siblings, 0 replies; 23+ messages in thread From: Samuel Stirtzel @ 2013-03-20 12:14 UTC (permalink / raw) To: openembedded-devel, martin.jansa, raj.khem 2013/3/7 Martin Jansa <martin.jansa@gmail.com>: > On Thu, Mar 07, 2013 at 04:20:42PM +0100, Samuel Stirtzel wrote: >> 2013/3/7 Martin Jansa <martin.jansa@gmail.com>: >> > On Thu, Mar 07, 2013 at 01:09:38PM +0100, Samuel Stirtzel wrote: >> >> 2013/3/7 Koen Kooi <koen@dominion.thruhere.net>: >> >> > Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> >> >> > --- >> >> > README | 2 +- >> >> > 1 file changed, 1 insertion(+), 1 deletion(-) >> >> > >> >> > diff --git a/README b/README >> >> > index 0635e10..cab1e21 100644 >> >> > --- a/README >> >> > +++ b/README >> >> > @@ -10,7 +10,7 @@ Samuel Stirtzel <s.stirtzel@googlemail.com> >> >> > Contributors: >> >> > Copyright 2012 - Kai Kang >> >> > Copyright 2013 - Khem Raj >> >> > -Copyright 2012 - Koen Kooi >> >> > +Copyright 2012, 2013 - Koen Kooi >> >> > Copyright 2012 - Robert Yang >> >> > Copyright 2011, 2012 - Samuel Stirtzel >> >> > >> >> > -- >> >> > 1.8.1.4 >> >> > >> >> >> >> Thanks for your patches, >> >> I applied them all. >> > >> > Can you update status on: >> > http://patches.openembedded.org/bundle/jama/meta-kde/?archive=both >> > >> > To keep patchwork clean? >> > >> >> I would, but unfortunately I have no Patchwork account. >> Also there seems to be no possibility to register a new account. > > Adding khem to CC: I guess he can arrange account for you. > Hi, so far I did not receive any info on how to create / access a patchwork account. Maybe something went wrong / got lost in transmission? -- Regards Samuel ^ permalink raw reply [flat|nested] 23+ messages in thread
end of thread, other threads:[~2013-03-20 12:31 UTC | newest] Thread overview: 23+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2013-03-07 9:50 [meta-kde][PATCH 1/3] packagegroup-kde-apps: remove multiline comment Koen Kooi 2013-03-07 9:50 ` [meta-kde][PATCH 2/3] ark, gwenview: fix RDEPENDS Koen Kooi 2013-03-07 9:50 ` [meta-kde][PATCH 3/3] README: update contributor list Koen Kooi 2013-03-07 12:09 ` Samuel Stirtzel 2013-03-07 13:04 ` Martin Jansa 2013-03-07 14:03 ` Koen Kooi 2013-03-07 14:35 ` Paul Eggleton 2013-03-07 14:41 ` Otavio Salvador 2013-03-07 14:50 ` Philip Balister 2013-03-07 15:05 ` Burton, Ross 2013-03-07 15:15 ` Burton, Ross 2013-03-07 15:18 ` Koen Kooi 2013-03-07 15:24 ` Richard Purdie 2013-03-07 15:41 ` Paul Eggleton 2013-03-11 12:34 ` Peter A. Bigot 2013-03-07 14:52 ` Martin Jansa 2013-03-07 15:30 ` Richard Purdie 2013-03-07 13:10 ` Paul Eggleton 2013-03-07 14:04 ` Samuel Stirtzel 2013-03-07 15:05 ` Martin Jansa 2013-03-07 15:20 ` Samuel Stirtzel 2013-03-07 15:56 ` Martin Jansa 2013-03-20 12:14 ` Samuel Stirtzel
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.