Skip to contentSkip to conversation

poky.conf: explicitly referenced preferred linux-yocto version

PATCH In review Bruce Ashfield 5 participants 9 messages Jul 25, 2011 – Aug 18, 2011

lore
Share & tools
lore
#0 lore raw

cover poky.conf: explicitly referenced preferred linux-yocto version

Here's a similar change to the meta-yocto boards, as was done to the qemu machines in oe-core. Since referencing yocto makes more sense in this layer, I made the change in the poky.conf distro default file.

As the staging of linux-yocto-3.0 showed, we should explicitly state our preferred version of linux-yocto. This prevents unvalidated changes from being forced into machines. Layers and machines are free to override this as they are updated.

cc Tom Zanussi <[email protected]>

The following changes since commit dfec64a66e66ad4ec94a06ad900307fb0d932b98:

machine/qemu: set preferred linux-yocto kernel version (2011-07-25 10:56:46 -0400)

are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel-yocto
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-yocto

Bruce Ashfield (1):
poky.conf: explicitly referenced preferred linux-yocto version

 meta-yocto/conf/distro/poky.conf |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)
Signature · 1 line
1.7.4.1
#1 lore raw

PATCH 1/1 poky.conf: explicitly referenced preferred linux-yocto version

As the staging of linux-yocto-3.0 showed, we should explicitly state our preferred version of linux-yocto. This prevents unvalidated changes from being forced into machines. Layers and machines are free to override this as they are updated.

---
 meta-yocto/conf/distro/poky.conf |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)
meta-yocto/conf/distro/poky.conf +2 -0
index 1ae94a0..88b8adf 100644
@@ -12,6 +12,8 @@ LOCALCONF_VERSION = "1"
 
 DISTRO_FEATURES_append = " largefile"
 
+PREFERRED_VERSION_linux-yocto ?= "2.6.37+git%"
+
 SDK_NAME = "${DISTRO}-${TCLIBC}-${SDK_ARCH}-${TARGET_ARCH}"
 SDKPATH = "/opt/${DISTRO}/${SDK_VERSION}"
 
Signature · 1 line
1.7.4.1
#2 lore raw
In reply to Bruce Ashfield
Quoted 20 lines · Bruce Ashfield

Here's a similar change to the meta-yocto boards, as was done to the qemu machines in oe-core. Since referencing yocto makes more sense in this layer, I made the change in the poky.conf distro default file.

As the staging of linux-yocto-3.0 showed, we should explicitly state our preferred version of linux-yocto. This prevents unvalidated changes from being forced into machines. Layers and machines are free to override this as they are updated.

cc Tom Zanussi <[email protected]>

The following changes since commit dfec64a66e66ad4ec94a06ad900307fb0d932b98:

machine/qemu: set preferred linux-yocto kernel version (2011-07-25 10:56:46 -0400)

are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel-yocto
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-yocto

Quoted 5 lines

Bruce Ashfield (1):
poky.conf: explicitly referenced preferred linux-yocto version

 meta-yocto/conf/distro/poky.conf |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

I guess as an aside, the convention we have/had in oe.dev was DEFAULT_PREFERENCE = -1, D_P_testedmachine1 = 1, etc, etc, in the kernel recipes.

Signature · 2 lines
Tom Rini
Mentor Graphics Corporation
#3 lore raw
Quoted 24 lines · Tom Rini
Quoted 23 lines · Bruce Ashfield

Here's a similar change to the meta-yocto boards, as was done to the qemu machines in oe-core. Since referencing yocto makes more sense in this layer, I made the change in the poky.conf distro default file.

As the staging of linux-yocto-3.0 showed, we should explicitly state our preferred version of linux-yocto. This prevents unvalidated changes from being forced into machines. Layers and machines are free to override this as they are updated.

cc Tom Zanussi <[email protected]>

The following changes since commit dfec64a66e66ad4ec94a06ad900307fb0d932b98:

  machine/qemu: set preferred linux-yocto kernel version (2011-07-25 10:56:46 -0400)

are available in the git repository at:
  git://git.pokylinux.org/poky-contrib zedd/kernel-yocto
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-yocto

Bruce Ashfield (1):
  poky.conf: explicitly referenced preferred linux-yocto version

Quoted 6 lines
Quoted 2 lines

 meta-yocto/conf/distro/poky.conf |    2 ++

 1 files changed, 2 insertions(+), 0 deletions(-)

I guess as an aside, the convention we have/had in oe.dev was DEFAULT_PREFERENCE = -1, D_P_testedmachine1 = 1, etc, etc, in the kernel recipes.

I've noticed that .. and it would work here as well. I'm hesitant to maintain a set of tested machine overrides in the yocto layers, since we are at a small number now, but that number isn't guaranteed to stay small. I have enough of a pain updating SRCREVs constantly, tweaking another set of vars isn't high on my 'fun' list.

I prefer to have the machines opt-in, versus maintaining a list of known good machines in a central file (I realize that the machines would/could be the ones setting the default_preference back to 1 as wel, but it is still another variable to manipulate). But am not religious about any of this :)

The flip to 3.0 is sort of a special case, and typically it is just a switch I throw, since all machines are tested at once.

Good comment and food for thought indeed!

Cheers,

Bruce

Quoted 9 lines

--
Tom Rini
Mentor Graphics Corporation
_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky

Signature · 2 lines
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
#4 lore raw
Quoted 43 lines · Bruce Ashfield
Quoted 24 lines · Tom Rini
Quoted 23 lines · Bruce Ashfield

Here's a similar change to the meta-yocto boards, as was done to the qemu machines in oe-core. Since referencing yocto makes more sense in this layer, I made the change in the poky.conf distro default file.

As the staging of linux-yocto-3.0 showed, we should explicitly state our preferred version of linux-yocto. This prevents unvalidated changes from being forced into machines. Layers and machines are free to override this as they are updated.

cc Tom Zanussi <[email protected]>

The following changes since commit dfec64a66e66ad4ec94a06ad900307fb0d932b98:

machine/qemu: set preferred linux-yocto kernel version (2011-07-25 10:56:46 -0400)

are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel-yocto
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-yocto

Bruce Ashfield (1):
poky.conf: explicitly referenced preferred linux-yocto version

Quoted 6 lines
Quoted 2 lines
 meta-yocto/conf/distro/poky.conf |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

I guess as an aside, the convention we have/had in oe.dev was DEFAULT_PREFERENCE = -1, D_P_testedmachine1 = 1, etc, etc, in the kernel recipes.

I've noticed that .. and it would work here as well. I'm hesitant to maintain a set of tested machine overrides in the yocto layers, since we are at a small number now, but that number isn't guaranteed to stay small. I have enough of a pain updating SRCREVs constantly, tweaking another set of vars isn't high on my 'fun' list.

I prefer to have the machines opt-in, versus maintaining a list of known good machines in a central file (I realize that the machines would/could be the ones setting the default_preference back to 1 as wel, but it is still another variable to manipulate). But am not religious about any of this :)

Quoted 4 lines

The flip to 3.0 is sort of a special case, and typically it is just a switch I throw, since all machines are tested at once.

Good comment and food for thought indeed!

So, if you go down the D_P route, meta-$whatever has linux_testedVer.bbappend D_P = "1" in it for what it wants to opt into and the meta-yocto / oe-core recipes just stay having to track qemu machines, too.

Signature · 2 lines
Tom Rini
Mentor Graphics Corporation
#5 lore raw
Quoted 47 lines · Tom Rini
Quoted 46 lines · Bruce Ashfield
Quoted 24 lines · Tom Rini
Quoted 23 lines · Bruce Ashfield

Here's a similar change to the meta-yocto boards, as was done to the qemu machines in oe-core. Since referencing yocto makes more sense in this layer, I made the change in the poky.conf distro default file.

As the staging of linux-yocto-3.0 showed, we should explicitly state our preferred version of linux-yocto. This prevents unvalidated changes from being forced into machines. Layers and machines are free to override this as they are updated.

cc Tom Zanussi <[email protected]>

The following changes since commit dfec64a66e66ad4ec94a06ad900307fb0d932b98:

  machine/qemu: set preferred linux-yocto kernel version (2011-07-25 10:56:46 -0400)

are available in the git repository at:
  git://git.pokylinux.org/poky-contrib zedd/kernel-yocto
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-yocto

Bruce Ashfield (1):
  poky.conf: explicitly referenced preferred linux-yocto version

Quoted 6 lines
Quoted 2 lines

 meta-yocto/conf/distro/poky.conf |    2 ++

 1 files changed, 2 insertions(+), 0 deletions(-)

I guess as an aside, the convention we have/had in oe.dev was DEFAULT_PREFERENCE = -1, D_P_testedmachine1 = 1, etc, etc, in the kernel recipes.

I've noticed that .. and it would work here as well. I'm hesitant to maintain a set of tested machine overrides in the yocto layers, since we are at a small number now, but that number isn't guaranteed to stay small. I have enough of a pain updating SRCREVs constantly, tweaking another set of vars isn't high on my 'fun' list.

I prefer to have the machines opt-in, versus maintaining a list of known good machines in a central file (I realize that the machines would/could be the ones setting the default_preference back to 1 as wel, but it is still another variable to manipulate). But am not religious about any of this :)

The flip to 3.0 is sort of a special case, and typically it is just a switch I throw, since all machines are tested at once.

Quoted 6 lines
Quoted 1 line

Good comment and food for thought indeed!

So, if you go down the D_P route, meta-$whatever has linux_testedVer.bbappend D_P = "1" in it for what it wants to opt into and the meta-yocto / oe-core recipes just stay having to track qemu machines, too.

Understood, that's what I tried to say (badly) when I mentioned that the machines could set this variable in their own layer, versus a central update.

The question that pops up for me, what's the pros and cons of this versus the machine setting a version preference by machine specific overrides (maybe they can't?) or setting their compatibility variables. I can see that this is an explicit statement of tested versus not tested, versus something more implicit. But are there others ?

Cheers,

Bruce

Quoted 5 lines

--
Tom Rini
Mentor Graphics Corporation

Signature · 2 lines
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
#6 lore raw
Quoted 59 lines · Bruce Ashfield
Quoted 47 lines · Tom Rini
Quoted 46 lines · Bruce Ashfield
Quoted 24 lines · Tom Rini
Quoted 23 lines · Bruce Ashfield

Here's a similar change to the meta-yocto boards, as was done to the qemu machines in oe-core. Since referencing yocto makes more sense in this layer, I made the change in the poky.conf distro default file.

As the staging of linux-yocto-3.0 showed, we should explicitly state our preferred version of linux-yocto. This prevents unvalidated changes from being forced into machines. Layers and machines are free to override this as they are updated.

cc Tom Zanussi <[email protected]>

The following changes since commit dfec64a66e66ad4ec94a06ad900307fb0d932b98:

machine/qemu: set preferred linux-yocto kernel version (2011-07-25 10:56:46 -0400)

are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel-yocto
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-yocto

Bruce Ashfield (1):
poky.conf: explicitly referenced preferred linux-yocto version

Quoted 6 lines
Quoted 2 lines
 meta-yocto/conf/distro/poky.conf |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

I guess as an aside, the convention we have/had in oe.dev was DEFAULT_PREFERENCE = -1, D_P_testedmachine1 = 1, etc, etc, in the kernel recipes.

I've noticed that .. and it would work here as well. I'm hesitant to maintain a set of tested machine overrides in the yocto layers, since we are at a small number now, but that number isn't guaranteed to stay small. I have enough of a pain updating SRCREVs constantly, tweaking another set of vars isn't high on my 'fun' list.

I prefer to have the machines opt-in, versus maintaining a list of known good machines in a central file (I realize that the machines would/could be the ones setting the default_preference back to 1 as wel, but it is still another variable to manipulate). But am not religious about any of this :)

The flip to 3.0 is sort of a special case, and typically it is just a switch I throw, since all machines are tested at once.

Quoted 6 lines
Quoted 1 line

Good comment and food for thought indeed!

So, if you go down the D_P route, meta-$whatever has linux_testedVer.bbappend D_P = "1" in it for what it wants to opt into and the meta-yocto / oe-core recipes just stay having to track qemu machines, too.

Understood, that's what I tried to say (badly) when I mentioned that the machines could set this variable in their own layer, versus a central update.

Quoted 5 lines

The question that pops up for me, what's the pros and cons of this versus the machine setting a version preference by machine specific overrides (maybe they can't?) or setting their compatibility variables. I can see that this is an explicit statement of tested versus not tested, versus something more implicit. But are there others ?

To me, it boils down to where do you make the pain point. If it's in the kernel recipe (/ bbappend), we don't cause a re-parse of the metadata. It can however be arguably more of a surprise when the kernel upgrades. With my Mentor hat, we've always pinned the recipe version down for the kernel, but with my community hat, building the latest that's supposed to work feels best.

Signature · 2 lines
Tom Rini
Mentor Graphics Corporation
#7 lore raw
Quoted 66 lines · Tom Rini
Quoted 59 lines · Bruce Ashfield
Quoted 47 lines · Tom Rini
Quoted 46 lines · Bruce Ashfield
Quoted 24 lines · Tom Rini
Quoted 23 lines · Bruce Ashfield

Here's a similar change to the meta-yocto boards, as was done to the qemu machines in oe-core. Since referencing yocto makes more sense in this layer, I made the change in the poky.conf distro default file.

As the staging of linux-yocto-3.0 showed, we should explicitly state our preferred version of linux-yocto. This prevents unvalidated changes from being forced into machines. Layers and machines are free to override this as they are updated.

cc Tom Zanussi <[email protected]>

The following changes since commit dfec64a66e66ad4ec94a06ad900307fb0d932b98:

machine/qemu: set preferred linux-yocto kernel version (2011-07-25 10:56:46 -0400)

are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel-yocto
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-yocto

Bruce Ashfield (1):
poky.conf: explicitly referenced preferred linux-yocto version

Quoted 6 lines
Quoted 2 lines
 meta-yocto/conf/distro/poky.conf |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

I guess as an aside, the convention we have/had in oe.dev was DEFAULT_PREFERENCE = -1, D_P_testedmachine1 = 1, etc, etc, in the kernel recipes.

I've noticed that .. and it would work here as well. I'm hesitant to maintain a set of tested machine overrides in the yocto layers, since we are at a small number now, but that number isn't guaranteed to stay small. I have enough of a pain updating SRCREVs constantly, tweaking another set of vars isn't high on my 'fun' list.

I prefer to have the machines opt-in, versus maintaining a list of known good machines in a central file (I realize that the machines would/could be the ones setting the default_preference back to 1 as wel, but it is still another variable to manipulate). But am not religious about any of this :)

The flip to 3.0 is sort of a special case, and typically it is just a switch I throw, since all machines are tested at once.

Quoted 6 lines
Quoted 1 line

Good comment and food for thought indeed!

So, if you go down the D_P route, meta-$whatever has linux_testedVer.bbappend D_P = "1" in it for what it wants to opt into and the meta-yocto / oe-core recipes just stay having to track qemu machines, too.

Understood, that's what I tried to say (badly) when I mentioned that the machines could set this variable in their own layer, versus a central update.

Quoted 5 lines

The question that pops up for me, what's the pros and cons of this versus the machine setting a version preference by machine specific overrides (maybe they can't?) or setting their compatibility variables. I can see that this is an explicit statement of tested versus not tested, versus something more implicit. But are there others ?

Quoted 6 lines

To me, it boils down to where do you make the pain point. If it's in the kernel recipe (/ bbappend), we don't cause a re-parse of the metadata. It can however be arguably more of a surprise when the kernel upgrades. With my Mentor hat, we've always pinned the recipe version down for the kernel, but with my community hat, building the latest that's supposed to work feels best.

How do DEFAULT_PREFERENCE and PREFERRED_VERSION relate to each other? Does one trump the other?

Signature · 3 lines
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
#8 lore raw
Quoted 2 lines · On Thursday 18 August 2011 19:25:48 Darren Hart wrote:

How do DEFAULT_PREFERENCE and PREFERRED_VERSION relate to each other? Does one trump the other?

DEFAULT_PREFERENCE is intentionally weak (says RP) and will be overridden by PREFERRED_VERSION_packagename if the latter is specified.

Cheers,
Paul

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre