Le 15/12/2014 15:11, ronan a écrit : > > > > Benefit: > 1) It ensures compatibility of systemd path to Tizen packages. Compatibility with legacy could be done with a simple link. > > 2) Faster integration of the Tizen packages into yocto project (less > path issue to be fixed). > Compatibility with legacy could be done with a simple link. > 3) Tizen doesn't use boot on /lib only (/usr/lib is mandatory for > Tizen Boot, more generally /usr), so no need to have systemd unit > system under /lib > > 4) meta-tizen is only for Tizen-distro so no need to ensure > compatibility with meta yocto. Yes, but we also aim at easing OE and Yocto packages integration. > > Disadvantage: > 1) If we have systemd under /lib we can boot system whitout /usr like > yocto (tiny system). Without we can't. +2. This is the biggest value of Yocto model and we should adopt it in Tizen. > > 2) If some Tizen package use path /usr/lib/systemd/system for systemd > unit system, no issues are raised for Tizen-distro but the package > from meta-yocto will not be compatible with yocto Project path. Less of a real issue as long as those services are not critical for boot a link can cover that. But it's always nice to get a clean code. > > > If it's OK for every one I'm going to merge the review 32000 into > meta-tizen. > Sorry, but I would rather stick to the Yocto model as being able to boot on a reduce file system is a real value add. Backward compatibility with old non standard hard-wired path in Tizen can always be enable via a simple link in Tizen. Obviously the correct use of the rpm macro is to be preferred.
Regards -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
