making building master-next just a little bit easier

making building master-next just a little bit easier

[Christian Betz]

hi everyone.

i've cloned fsl-community-bsp-platform and created a master-next
branch with the correct repo XML file to use master-next branch for
all the meta-fsl-* repos and master for the rest. this makes building
and testing master-next from scratch a bit easier.

this was pretty trivial to do but I wanted to mention it to the list.
i'd be happy to submit "official" patches to the list for these
changes if desired.

so instead of the normal dylan build:

repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b dylan

I do this to build master-next using the repo XML on my cloned github repo:

repo init -u https://github.com/cbetz421/fsl-community-bsp-platform -b
master-next

NOTE: I also updated the README in my master-next branch (but I
suggest that the README in master also should be updated to replace
"-b dylan" with "-b master").

--christian

Re: making building master-next just a little bit easier

[Eric Nelson]

Thanks Christian,

On 08/27/2013 10:36 AM, Christian Betz wrote:
> hi everyone.
>
> i've cloned fsl-community-bsp-platform and created a master-next
> branch with the correct repo XML file to use master-next branch for
> all the meta-fsl-* repos and master for the rest. this makes building
> and testing master-next from scratch a bit easier.
>
> this was pretty trivial to do but I wanted to mention it to the list.
> i'd be happy to submit "official" patches to the list for these
> changes if desired.
>

+1

This is useful.

> so instead of the normal dylan build:
>
> repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b dylan
>
> I do this to build master-next using the repo XML on my cloned github repo:
>
> repo init -u https://github.com/cbetz421/fsl-community-bsp-platform -b
> master-next
>
> NOTE: I also updated the README in my master-next branch (but I
> suggest that the README in master also should be updated to replace
> "-b dylan" with "-b master").
>

Re: making building master-next just a little bit easier

[John Weber]

On 8/27/13 12:53 PM, Eric Nelson wrote:
> Thanks Christian,
>
> On 08/27/2013 10:36 AM, Christian Betz wrote:
>> hi everyone.
>>
>> i've cloned fsl-community-bsp-platform and created a master-next
>> branch with the correct repo XML file to use master-next branch for
>> all the meta-fsl-* repos and master for the rest. this makes building
>> and testing master-next from scratch a bit easier.
>>
>> this was pretty trivial to do but I wanted to mention it to the list.
>> i'd be happy to submit "official" patches to the list for these
>> changes if desired.
>>
>
> +1
>
> This is useful.
Agreed, and I'm sure Otavio would love some patches to review.  Glad to see that 
it does not checkout master-next from Poky or OE.
>
>> so instead of the normal dylan build:
>>
>> repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b dylan
>>
>> I do this to build master-next using the repo XML on my cloned github repo:
>>
>> repo init -u https://github.com/cbetz421/fsl-community-bsp-platform -b
>> master-next
>>
>> NOTE: I also updated the README in my master-next branch (but I
>> suggest that the README in master also should be updated to replace
>> "-b dylan" with "-b master").
>>
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale

Re: making building master-next just a little bit easier

[Otavio Salvador]

On Tue, Aug 27, 2013 at 3:52 PM, John Weber <rjohnweber@gmail.com> wrote:
>
> On 8/27/13 12:53 PM, Eric Nelson wrote:
>>
>> Thanks Christian,
>>
>> On 08/27/2013 10:36 AM, Christian Betz wrote:
>>>
>>> hi everyone.
>>>
>>> i've cloned fsl-community-bsp-platform and created a master-next
>>> branch with the correct repo XML file to use master-next branch for
>>> all the meta-fsl-* repos and master for the rest. this makes building
>>> and testing master-next from scratch a bit easier.
>>>
>>> this was pretty trivial to do but I wanted to mention it to the list.
>>> i'd be happy to submit "official" patches to the list for these
>>> changes if desired.
>>>
>>
>> +1
>>
>> This is useful.
>
> Agreed, and I'm sure Otavio would love some patches to review.  Glad to see
> that it does not checkout master-next from Poky or OE.

Patches please?! ;-)

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

Re: making building master-next just a little bit easier

[Christian Betz]

On Thu, Aug 29, 2013 at 4:03 PM, Otavio Salvador
<otavio@ossystems.com.br> wrote:
> On Tue, Aug 27, 2013 at 3:52 PM, John Weber <rjohnweber@gmail.com> wrote:
>>
>> On 8/27/13 12:53 PM, Eric Nelson wrote:
>>>
>>> Thanks Christian,
>>>
>>> On 08/27/2013 10:36 AM, Christian Betz wrote:
>>>>
>>>> hi everyone.
>>>>
>>>> i've cloned fsl-community-bsp-platform and created a master-next
>>>> branch with the correct repo XML file to use master-next branch for
>>>> all the meta-fsl-* repos and master for the rest. this makes building
>>>> and testing master-next from scratch a bit easier.
>>>>
>>>> this was pretty trivial to do but I wanted to mention it to the list.
>>>> i'd be happy to submit "official" patches to the list for these
>>>> changes if desired.
>>>>
>>>
>>> +1
>>>
>>> This is useful.
>>
>> Agreed, and I'm sure Otavio would love some patches to review.  Glad to see
>> that it does not checkout master-next from Poky or OE.
>
> Patches please?! ;-)

actually... it turns out there is a master-next in poky... and I
needed a particular change from it it in order to build python (and
therefore fsl-image-test) cleanly. [1]

what do you think? should fsl-community-bsp-platform master-next
branch point at poky master-next also? i'll whip up the patches right
away after this is answered. there will be two patches that I assume
you will apply in sequence:

(1) patch against fsl-community-bsp-platform master branch that fixes
the README instructions to use 'master' instead of 'dylan'
(2) patch against fsl_community-bsp-platform master branch (which
assumes patch #1 landed) that fixes the README to say 'master-next'
instead of 'master' and also changes branches to master-next in the
default.xml. of course this would need to be applied in a new branch
called master-next.

due to the fact that the second patch is going into its own branch i
am hesitating to call this a "patch series". but i'm glad to submit
the patches however you prefer.

--christian

--christian

1. http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=master-next&id=5a2b592417570313f9a65b67e26d19ca5db95fb6

>
> --
> Otavio Salvador                             O.S. Systems
> http://www.ossystems.com.br        http://code.ossystems.com.br
> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale



-- 
"the new garbage collector will be an arena-based, quad-color
incremental, generational, non-copying, high-speed, cache-optimized
garbage collector" -- LuaJIT Roadmap

Re: making building master-next just a little bit easier

[Daiane Angolini]

On 08/30/2013 03:48 AM, Christian Betz wrote:
> On Thu, Aug 29, 2013 at 4:03 PM, Otavio Salvador
> <otavio@ossystems.com.br> wrote:
>> On Tue, Aug 27, 2013 at 3:52 PM, John Weber <rjohnweber@gmail.com> wrote:
>>>
>>> On 8/27/13 12:53 PM, Eric Nelson wrote:
>>>>
>>>> Thanks Christian,
>>>>
>>>> On 08/27/2013 10:36 AM, Christian Betz wrote:
>>>>>
>>>>> hi everyone.
>>>>>
>>>>> i've cloned fsl-community-bsp-platform and created a master-next
>>>>> branch with the correct repo XML file to use master-next branch for
>>>>> all the meta-fsl-* repos and master for the rest. this makes building
>>>>> and testing master-next from scratch a bit easier.
>>>>>
>>>>> this was pretty trivial to do but I wanted to mention it to the list.
>>>>> i'd be happy to submit "official" patches to the list for these
>>>>> changes if desired.
>>>>>
>>>>
>>>> +1
>>>>
>>>> This is useful.
>>>
>>> Agreed, and I'm sure Otavio would love some patches to review.  Glad to see
>>> that it does not checkout master-next from Poky or OE.
>>
>> Patches please?! ;-)
>
> actually... it turns out there is a master-next in poky... and I
> needed a particular change from it it in order to build python (and
> therefore fsl-image-test) cleanly. [1]
>
> what do you think? should fsl-community-bsp-platform master-next
> branch point at poky master-next also? i'll whip up the patches right
> away after this is answered. there will be two patches that I assume
> you will apply in sequence:

I talked to Otavio on the phone, and he asked me to reply here (he's 
going to be offline for some hours)

He prefers (and I agree) that uses poky master-next is not the best for 
us. Poky master-next does not act like meta-fsl-arm master-next, and 
sometimes it's behind master.

And, (now you read it with my voice) I think our master-next is 
basically for testing, and use poky/master-next includes a second 
variable that we cannot control on meta-fsl-arm test.

>
> (1) patch against fsl-community-bsp-platform master branch that fixes
> the README instructions to use 'master' instead of 'dylan'

I may say it's a trick change. Mostly we want users to be on latest 
stable branch (developers on master), and if you see on github the 
default README file shown is the master one. So the default 
"recomendation" would be stay on latest stable.

I'm not sure if I made me clean. Please, let me know any doubt.

> (2) patch against fsl_community-bsp-platform master branch (which
> assumes patch #1 landed) that fixes the README to say 'master-next'
> instead of 'master' and also changes branches to master-next in the
> default.xml. of course this would need to be applied in a new branch
> called master-next.
>
> due to the fact that the second patch is going into its own branch i
> am hesitating to call this a "patch series". but i'm glad to submit
> the patches however you prefer.
>
> --christian
>
> --christian
>
> 1. http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=master-next&id=5a2b592417570313f9a65b67e26d19ca5db95fb6
>
>>
>> --
>> Otavio Salvador                             O.S. Systems
>> http://www.ossystems.com.br        http://code.ossystems.com.br
>> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
>> _______________________________________________
>> meta-freescale mailing list
>> meta-freescale@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-freescale
>
>
>


-- 
Daiane

Re: making building master-next just a little bit easier

[Christian Betz]

On Fri, Aug 30, 2013 at 10:23 AM, Daiane Angolini
<daiane.angolini@freescale.com> wrote:
> On 08/30/2013 03:48 AM, Christian Betz wrote:
>>
>> On Thu, Aug 29, 2013 at 4:03 PM, Otavio Salvador
>> <otavio@ossystems.com.br> wrote:
>>>
>>> On Tue, Aug 27, 2013 at 3:52 PM, John Weber <rjohnweber@gmail.com> wrote:
>>>>
>>>>
>>>> On 8/27/13 12:53 PM, Eric Nelson wrote:
>>>>>
>>>>>
>>>>> Thanks Christian,
>>>>>
>>>>> On 08/27/2013 10:36 AM, Christian Betz wrote:
>>>>>>
>>>>>>
>>>>>> hi everyone.
>>>>>>
>>>>>> i've cloned fsl-community-bsp-platform and created a master-next
>>>>>> branch with the correct repo XML file to use master-next branch for
>>>>>> all the meta-fsl-* repos and master for the rest. this makes building
>>>>>> and testing master-next from scratch a bit easier.
>>>>>>
>>>>>> this was pretty trivial to do but I wanted to mention it to the list.
>>>>>> i'd be happy to submit "official" patches to the list for these
>>>>>> changes if desired.
>>>>>>
>>>>>
>>>>> +1
>>>>>
>>>>> This is useful.
>>>>
>>>>
>>>> Agreed, and I'm sure Otavio would love some patches to review.  Glad to
>>>> see
>>>> that it does not checkout master-next from Poky or OE.
>>>
>>>
>>> Patches please?! ;-)
>>
>>
>> actually... it turns out there is a master-next in poky... and I
>> needed a particular change from it it in order to build python (and
>> therefore fsl-image-test) cleanly. [1]
>>
>> what do you think? should fsl-community-bsp-platform master-next
>> branch point at poky master-next also? i'll whip up the patches right
>> away after this is answered. there will be two patches that I assume
>> you will apply in sequence:
>
>
> I talked to Otavio on the phone, and he asked me to reply here (he's going
> to be offline for some hours)
>
> He prefers (and I agree) that uses poky master-next is not the best for us.
> Poky master-next does not act like meta-fsl-arm master-next, and sometimes
> it's behind master.
>
> And, (now you read it with my voice) I think our master-next is basically
> for testing, and use poky/master-next includes a second variable that we
> cannot control on meta-fsl-arm test.

thank you. that's why i asked.

>
>
>>
>> (1) patch against fsl-community-bsp-platform master branch that fixes
>> the README instructions to use 'master' instead of 'dylan'
>
>
> I may say it's a trick change. Mostly we want users to be on latest stable
> branch (developers on master), and if you see on github the default README
> file shown is the master one. So the default "recomendation" would be stay
> on latest stable.

this was my understanding and still is but perhaps it did need clarification.

i think we're just in a situation now where there are hotly
anticipated things like x11 opengl acceleration and qt5 in master and
then some of those things don't work so we try master-next. the
"users" are getting anxious and putting on their "developer" hats.
this is maybe even desirable, but only to the extent that the existing
developers aren't distracted by having to get all the new "developers"
up to speed.

what i'm trying to say is that i really appreciate both of your
efforts. i didn't mean to cause confusion or distraction for the user
base.

>
> I'm not sure if I made me clean. Please, let me know any doubt.

i'm not sure i was clear either. regarding the README:

* the default branch on github when you go the project is the dylan
branch, the README contains dylan in the instructions.
* the master branch README contains dylan in the instructions:
** https://github.com/Freescale/fsl-community-bsp-platform/blob/master/README
** right now i consider myself a user, tester, and a developer. it's a
convenience to have 'dylan', 'master' or 'master-next' show up in the
instructions when I select a different branch from the dropdown in
github
*** this is because I am lazy and forgetful ;)

i'm going to forget about the README for now and will make a separate
patch if my lazyness argument is convincing to anyone.

to recap: ONE patch for default.xml without any README changes will be
forthcoming tonight.

--christian

>
>
>> (2) patch against fsl_community-bsp-platform master branch (which
>> assumes patch #1 landed) that fixes the README to say 'master-next'
>> instead of 'master' and also changes branches to master-next in the
>> default.xml. of course this would need to be applied in a new branch
>> called master-next.
>>
>> due to the fact that the second patch is going into its own branch i
>> am hesitating to call this a "patch series". but i'm glad to submit
>> the patches however you prefer.
>>
>> --christian
>>
>> --christian
>>
>> 1.
>> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=master-next&id=5a2b592417570313f9a65b67e26d19ca5db95fb6
>>
>>>
>>> --
>>> Otavio Salvador                             O.S. Systems
>>> http://www.ossystems.com.br        http://code.ossystems.com.br
>>> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
>>> _______________________________________________
>>> meta-freescale mailing list
>>> meta-freescale@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/meta-freescale
>>
>>
>>
>>
>
>
> --
> Daiane
>



-- 
"the new garbage collector will be an arena-based, quad-color
incremental, generational, non-copying, high-speed, cache-optimized
garbage collector" -- LuaJIT Roadmap

Re: making building master-next just a little bit easier

[Daiane Angolini]

> i'm not sure i was clear either. regarding the README:
>
> * the default branch on github when you go the project is the dylan
> branch, the README contains dylan in the instructions.
> * the master branch README contains dylan in the instructions:
> ** https://github.com/Freescale/fsl-community-bsp-platform/blob/master/README
> ** right now i consider myself a user, tester, and a developer. it's a
> convenience to have 'dylan', 'master' or 'master-next' show up in the
> instructions when I select a different branch from the dropdown in
> github
> *** this is because I am lazy and forgetful ;)

It made me think that maybe, have all the command lines would be better.

all the command lines, and a description of what is what:

dylan - latest stable branch, for production

$ lalalalalalal -b dylan

master - development branch, where things happens

$ alalaalalalal -b master

master-next - test branch, for fearless, intrepid developer

$ lalalala -b master-next


But, it also made me think that maybe we are overthinking this topic =P

>
> i'm going to forget about the README for now and will make a separate
> patch if my lazyness argument is convincing to anyone.
>
> to recap: ONE patch for default.xml without any README changes will be
> forthcoming tonight.
>
> --christian


-- 
Daiane