[yocto] 1.3_M5.rc2 status.

[Wolfgang Denk]

Dear Paul,

In message <224780988.1nyHnvScgz at helios> you wrote:
>
> > If meta layer specific values of LAYER_CONF_VERSION are allowed, the
> > sanity checker needs a better way to deal with these; alternatively,
> > above setting in meta-yocto/conf/distro/poky.conf is wrong.  So either
> > of these should be fixed.
> 
> By "better way to deal with these", what would you suggest? I don't see any 
> alternative that avoids the BSP components just disappearing for users who 
> have existing configurations.

Well, the comment in  "meta-yocto/conf/bblayers.conf.sample"  says:

	# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
	# changes incompatibly

This suggests that such changes are not exactly unusual.  But any such
change will cause the build to fail, because the sanity checker uses a
different value.

If such a change is allowed and is done intentionally, then it should
be considered "sane", and the sanity checker should not complain.

The problem (and the longer I think about it the less I hesitate to
call it a plain bug) is that we allow for meta layer specific values
of LAYER_CONF_VERSION, while still assuming a single hard-coded
value in  meta/conf/sanity.conf  could be used as reference.

This _cannot_ work.

But when I'm supposed to overwrite the setting (to match the sanity
checker's expectations) in my local conf/bblayers.conf, then why do we
bother to set a dieferent value in the meta layer in the first place?
And hey, why do we check this value at all if all we can do is always
make it match manually?

I understand the intention, but the current implementation is just
broken, and I don't see a way to fix it.  It would probably be better
to remove this test than to leave it as is.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
If a packet hits a pocket on a socket on a port,
And the bus is interrupted as a very last resort,
And the address of the memory makes your floppy disk abort,
Then the socket packet pocket has an error to report! - Ken Burchill?