I'm posting this for reference.
The variable SIGGEN_EXCLUDERECIPES_ABISAFE in layer.conf specifically
excludes the recipe base-files because it is never supposed to change.
The appropriate way to modify /etc/profile is to add customizations to
the directory /etc/profile.d.
On Fri, Jul 25, 2014
I'm on dora. I am using a different /etc/profile for base-files via a
bbappend. Subsequent builds of my image does not add the new
base-files package as I think it should.
Running bitbake of my image after the modification reports nothing to do.
Bumping the PR on the bbappend rebuilds base-files
On Fri, Jul 25, 2014 at 9:10 AM, Jate S jate...@gmail.com wrote:
I'm on dora. I am using a different /etc/profile for base-files via a
bbappend. Subsequent builds of my image does not add the new
base-files package as I think it should.
Running bitbake of my image after the modification
base-files_3.0.14.bbappend:
FILESEXTRAPATHS_prepend := ${THISDIR}/base-files:
PR := ${PR}.0
Here's output from the tree command.
recipes-core/base-files/
|-- base-files
| `-- profile
`-- base-files_3.0.14.bbappend
1 directory, 2 files
On Fri, Jul 25, 2014 at 1:30 PM, Khem Raj
