filesystem layout: configure via base-files instead of config-image
authorPatrick Ohly <patrick.ohly@intel.com>
Tue, 3 Feb 2015 14:39:23 +0000 (06:39 -0800)
committerPatrick Ohly <patrick.ohly@intel.com>
Tue, 3 Feb 2015 15:22:49 +0000 (07:22 -0800)
commit7936657883215d19e2eb4877a766d08ee70bce2c
tree4dcba2bca259396d940a54f0390b428859cd7881
parentf23b8be3eef0fb60d3a3235cc3064637fb57eb26
filesystem layout: configure via base-files instead of config-image

Changing file permissions via postinst is bad style, for example,
rpm cannot be used to determine why permissions were set this way.
The right way of solving this is via rpm manifest files.

The whole custom config-image can be replaced with a modified base-file
that has a manifest file and DIRFILES_${PN} set up accordingly.

In adddition, this commit also makes "Tizen on Yocto" more like Tizen:
- no more /var/volation - that dependend on a systemd unit from OE
  that was not even present in "Tizen on Yocto"
- /sbin /lib and /bin are now symlinks to /usr

The advantage of these symlinks are that recipes from Tizen which
contain hard-coded paths will work without having to be fixed. It is
uncertain whether there *are* any such recipes at the moment, but
there might be some or might be in the future.

The real advantage right now is that it makes it simpler to compare
file systems from Tizen and "Tizen on Yocto".

Change-Id: I2a1dbdc6de58cdfd245a3c42b6f7a0f8855cb97d
meta-tizen-adaptation/meta/files/tizen-fs-perms.txt [new file with mode: 0644]
meta-tizen-adaptation/meta/recipes-core/base-files/base-files/base-files.manifest [new file with mode: 0644]
meta-tizen-adaptation/meta/recipes-core/base-files/base-files_3.0.14.bbappend
meta-tizen-common-base/recipes-image/config-image/config-image.bb [deleted file]
meta-tizen-common-base/recipes-image/images/tizen-core-image-minimal.bb
meta-tizen-ivi/recipes-image/config-image/config-image.bbappend [deleted file]