On Fri, 2015-02-20 at 15:27 +0200, Leon Anavi wrote: > On 20.02.2015 12:31, Patrick Ohly wrote: > > These bashism issues should indeed be better fixed in the .spec files > > and not the .inc files derived from them, so this guide applies. > > > > However, it is uncertain whether working with non-bash shell > > interpreters is a goal for Tizen; at the moment it is not tested for > > consistently, neither in OBS nor in "Tizen on Yocto". So it is unclear > > whether maintainers will accept such patches. Worse, such issues may get > > re-introduced. > > > > Overall I think it's easier to accept that .inc files depend on bash and > > patch build.py in tizen-distro as suggested above. > > > > As far as I know Ubuntu is among the supported platforms for both Tizen > IVI application and platform development and its default system shell is > dash. In my opinion the change at the python scripts seems as a work > around. It will be more user/developer friendly and more convenient if > the Tizen build with Yocto works out of the box on Ubuntu.
Patching build.py in tizen-distro would achieve that, too. I know that this looks like avoiding the issue, but it's simply less work and more likely to succeed. If we want spec files to be free of bashisms (which is not needed for OBS and gbs, at least as far as I know), then this needs to be communicated clearly as a project goal, and it needs to be enforced as part of patch acceptance into the distro. As you noticed, Ronan has already tried for a long time to get spec files fixed, without success. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
