On Mon, 2006-11-27 at 21:46 +0100, Duncan Webb wrote: > AFAIK we're not using the inotify features, it's there because it's > needed by metadata. It's metadata that is really important as it > replaces mmpython.
I'll just repeat what I said on IRC for the record :) These files are necessary when the system's glibc doesn't have inotify support built in. If they're not included in that case, kaa-base will not build: creating build/temp.linux-i686-2.4/src/extensions/inotify gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -m32 -march=i386 -mtune=pentium4 -fasynchronous-unwind-tables -D_GNU_SOURCE -fPIC -fPIC -I/usr/include/python2.4 -c src/extensions/inotify/inotify.c -o build/temp.linux-i686-2.4/src/extensions/inotify/inotify.o -Wall src/extensions/inotify/inotify.c:38:33: error: fallback-inotify.h: No such file or directory src/extensions/inotify/inotify.c:39:42: error: fallback-inotify-syscalls.h: No such file or directory Even though kaa.metadata isn't using inotify features, these files are still part of kaa.base and should be included in any released bundle. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Freevo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freevo-devel
