Mirror of git.yoctoproject.org/poky https://git.enea.com/cgit/linux/poky.git/atom?h=2.3_M2 2016-06-02T07:24:02+00:00 2016-06-02T07:24:02+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2016-05-06T08:07:37+00:00 urn:sha1:deca1476459ab306dc5c80171fdf0d227decbea4 (Bitbake rev: 5ee80d77bc278758e411048ed09551ab65b9e72d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2015-01-14T11:32:02+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2015-01-13T14:11:36+00:00 urn:sha1:83f8a4002ab2026696973422ee0f5733652d9527 We need inotify support within bitbake and pyinotify provides the best mechanism to add this. We have a few options: a) Depend on pyinotify from the system b) Add in our own copy c) Only use pyinotify in cases like the memory resident server For a), it would mean adding in dependencies, updating documentation and generally creating churn for users as well as having implications for things like the build-appliance recipe. It turns out that glibc has the C functionality we need from version 2.4 onwards (2006) and that we just need a single python file for b), there is no binary module needed. We therefore add in a copy of pyinotify 0.9.5 into the tree meaning we can depend on it simply and unconditionally. c) is unattractive as we need fewer possible code paths, not more. (Bitbake rev: d49004a4e247e3958a2f7ea9ffe5ec92794e1352) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>