diff options
author | Richard Purdie <richard.purdie@linuxfoundation.org> | 2015-04-10 15:57:01 +0100 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2015-04-11 16:21:47 +0100 |
commit | 55303f7a3890347b2558d3c578125762675ecd96 (patch) | |
tree | cba99e1dfebd68cb071a43801e1c01a2c9cea29a /LICENSE | |
parent | 8a00b63e43efc7808e4fcc329ee0924af907a636 (diff) | |
download | poky-55303f7a3890347b2558d3c578125762675ecd96.tar.gz |
bitbake: bitbake: Add pyinotify to lib/
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)
(Bitbake rev: 2835b12288cf0c46586d6f708a0ee0b5e025cba3)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'LICENSE')
0 files changed, 0 insertions, 0 deletions