[yocto] update mechanisms

Philip Balister philip at balister.org
Tue Dec 6 10:45:09 PST 2016


On 12/06/2016 06:11 AM, Lopez, Mariano wrote:
> 
> 
> On 12/6/2016 3:45 AM, Patrick Ohly wrote:
>> On Tue, 2016-12-06 at 10:01 +0100, Stefano Babic wrote:
>>> Hi Patrick,
>>>
>>> On 30/11/2016 15:59, Patrick Ohly wrote:
>>>> I've started a Wiki page
>>>> https://wiki.yoctoproject.org/wiki/System_Update - rudimentary at the
>>>> moment, but might as well be mentioned already now.
>>> I have seen Mariano added an entry for SWUpdate, too, thanks  - I would
>>> like to edit for better explanation on some parts. Should I try to edit
>>> directly the page or is it better to discuss it here ?
> 
> It will be interesting to have your input directly, I tried to fill the
> table with my experience with SWUpdate but I think you could give a
> better insight of this. Thanks for joining the effort.
> 
>> Use your own judgment. If its uncontroversial, the feel free to edit the
>> page directly, otherwise let's discuss it here.
>>
>> If feel that putting information directly into the table is too limiting
>> (it should be brief), then feel free to start a complete section about
>> SWUpdate.
>>
>> I'll do the same for swupd. Editing the sections should be possible
>> without conflicts, we just have to be more careful about editing the
>> table concurrently.
>>
> 
> I agree with you, that we need to have a section per project, the table
> is too limiting.

I just skimmed the page and the table format isn't working well with the
length of the blocks of text.

I'd also suggest referencing Matt Porter's talk from ELCE 2016 about
software update technology:

http://elinux.org/images/3/31/Comparison_of_Linux_Software_Update_Technologies.pdf

https://youtu.be/pdHV9H9nZks?list=PLbzoR-pLrL6pRFP6SOywVJWdEHlmQE51q

Philip


> 
> Mariano



More information about the yocto mailing list