Re: PRServer's problem

[Robert Yang <liezhi.yang@windriver.com>]

On 05/19/2016 06:17 PM, Richard Purdie wrote:
> On Thu, 2016-05-19 at 18:12 +0800, Robert Yang wrote:
>> On 05/19/2016 05:45 PM, Richard Purdie wrote:
>>> To be really clear, OE-Core will not have a different signature
>>> policy
>>> on release branches since that differing policy would break user
>>> expectations and also wouldn't get tested apart from on the branch
>>> so
>>> we'd have less confidence it was working.
>>
>> Yes, I agree with this, I just used stable release as an example (big
>> changes won't happen on a stable release).
>>
>>>
>>> Users are free to set their own policies, the system was designed
>>> to do
>>> that. If WindRiver wants to have a much more permissive policy, I'm
>>> more than happy for them to do so.
>>
>> Thanks, frankly speaking, not only WindRiver wants this. After cloud
>> computing and virtualization gets hot, more and more users want to
>> customize their own images (for saving disk space, memory and
>> security
>> reason), oe/yocto is very good at customizing images, so more and
>> more people try to use it to build their own distros, where live
>> upgrades becomes very important.
>
> I understand that. So are we going to get binary diff working? Its the

Thanks everyone, it seems that this is the best way we have, I will
try packagefeed-stability class.

// Robert

> only viable solution we have to the problem at the moment that I know
> of. Randomly hacking bits of the signature generation isn't going to
> help this unfortunately.
>
> Cheers,
>
> Richard
>
>