[yocto] [meta-yocto][PATCH] poky.conf: Use weaker assignment for PREMIRROR

Khem Raj raj.khem at gmail.com
Wed Apr 3 00:19:51 PDT 2013


On Apr 2, 2013, at 11:56 PM, Paul Eggleton <paul.eggleton at linux.intel.com> wrote:

> On Tuesday 02 April 2013 23:44:06 Khem Raj wrote:
>> On Apr 2, 2013, at 11:41 PM, Paul Eggleton <paul.eggleton at linux.intel.com> 
> wrote:
>>> I'm not sure this is a path we should be going down; potentially we could
>>> end up having to use ??= for just about everything.
>> 
>> whats is downside of using ??= instead of ?=
> 
> The volume of changes to the config that this will require, a minor memory 
> usage increase (I suspect), but more importantly it increases the complexity 
> for the end user. Right now ??= is used sparingly.



> 
>>> Wouldn't you be better off using your own separate distro config (perhaps
>>> copying poky.conf instead of "require"ing it) and then the user can just
>>> set it with "=" ?
>> 
>> yes. however you are then always on lookout for changes happening in poky
>> policies then you need to mimic in your distro config
> 
> Wouldn't it be the reverse at the moment? We do add new things to the poky 
> distro config when we need to test them and those new things might not be 
> desirable in your configuration.
> 

no, if one is tracking upstream and wants to remain compatible its lot better to take in all policies
and then customize it. and once released the policies are not changed anyway. Its easier to test and customize
your distro that way since changes are incremental examples are when new QA checks are enabled you want to fix
your own layers quickly and its one less hassle to keep syncing policies when your distro and you can get quicker
response to fallouts if any. From personal experience including it has been a better way and indirectly is more integrated.

After all poky is a reference distro policy, whether we should recommend to copy it or include it in custom distros,
either ways is fine with good reasons. You sound like supporting the second case, I am impartial to whatever is the
recommendation there are good and bad of both approaches.

I am also interested in hearing from other yocto users how are they consuming poky policies 


> Distro configs should remain fairly static once initially set.

after releases yes but not when you are building next gen which is for active development.

> FWIW, we do call 
> out any needed changes between releases in the migration information within 
> the documentation.


yes as I said once needs to sync.


More information about the yocto mailing list