Re: [yocto] SVN based AUTOREV detection?

On Sat, Nov 07, 2015 at 01:52:37AM +, allen.cur...@curtisembedded.com wrote: > > Hello, > > Is there a way to use the feature during development when you are > working off trunk/HEAD? > > This doesn't work (obviously). Is it possible to pull the HEAD version > in the recipe? > >

Re: [yocto] [meta-raspberrypi] Missing config.txt in rpi-basic-image.bb

Hi, On Sat, Nov 7, 2015 at 12:17 PM, Chaitanya Dhere wrote: > Hello, > Thanks for your input. After doing a loopback mount, I was > able to locate the config.txt in that first partition. I modified that > config.txt as required and it worked. But the same

[yocto] [meta-selinux][PATCH 0/4] Reorganize SELinux early boot scripts.

With file system labeling support in the build now the init script in the selinux-config recipe has a lot of unnecessary checks / fixes. This patch set factors this script out into 3 new recipes: selinux-labeldev: The first init script that a system needs to run in order to get devices nodes

[yocto] [meta-selinux][PATCH 1/4] selinux-config: Separate init script into new recipe.

Add runtime dependencies for init script. Signed-off-by: Philip Tricca --- .../packagegroups/packagegroup-core-selinux.bb | 1 + .../packagegroups/packagegroup-selinux-minimal.bb | 1 + .../selinux/selinux-config/selinux-init.sh | 71 --

[yocto] [meta-selinux][PATCH 2/4] selinux-init: Move script logic into include.

This will be useful when we have other init scripts. Signed-off-by: Philip Tricca --- recipes-security/selinux/selinux-init_0.1.bb | 24 +++- recipes-security/selinux/selinux-initsh.inc | 25 + 2 files changed, 28 insertions(+), 21

Re: [yocto] [meta-selinux][PATCH] selinux-image: Fix RE error getting POL_TYPE

On 11/05/2015 08:56 AM, George McCollister wrote: > Change [:space:] to [[:space:]]. [:space:] is incorrect and is treated > as a list of characters. Prior to this change having a policy of > 'standard' resulted in POL_TYPE being set to 'tandard'. Good catch. > Change the regular expression to

Re: [yocto] SVN based AUTOREV detection?

Is there a way to use the feature during development when you are working off trunk/HEAD? This doesn't work (obviously). Is it possible to pull the HEAD version in the recipe? --- PR = "r0" PV = "0.1+svn${SRCPV}" SRCREV = "${AUTOREV}" SRC_URI =

[yocto] [Recipe reporting system] Upgradable recipe name list

This mail was sent out by Recipe reporting system. This message list those recipes which need to be upgraded. If maintainers believe some of them needn't to upgrade this time, they can fill in RECIPE_NO_UPDATE_REASON_pn-"xxx" in upstream_tracking files to ignore this recipe remainder until newer