The gnome-menus-2.18.2 ebuild has inotify support enabled by default. In order to make the ebuild *BSD-friendly, there needs to be an option to disable it (since inotify is a feature of the Linux kernel). There is no "inotify" global USE flag. There is a libnotify flag, but I am not sure if that is referring to the same thing. The problem with an inotify USE flag is that in order make the ebuild function the same way for Linux users (enabled by default), the inotify flag would have to be turned on in the Linux profiles and masked in the *BSD profiles(based on my beginner's knowledge of portage anyway). There is also the option of a "noinotify" flag which could be enabled by default in *BSD profiles. That is my $0.02.
What's wrong w/ something like G2CONF="$(use_enable !kernel_FreeBSD inotify) $(use_enable debug) $(use_enable python)" ?
What about : G2CONF="$(use_enable kernel_linux inotify) $(use_enable debug) $(use_enable python)" Just to be sure (I haven't look at gnome-menu's code) it's not using the gnome-vfs file monitoring api? That sounds shocking :) Something worth poking upstream about.
Created attachment 123160 [details, diff] gnome-menus-2.18.2.ebuild.diff (In reply to comment #2) > What about : > > G2CONF="$(use_enable kernel_linux inotify) $(use_enable debug) $(use_enable > python)" > > Just to be sure (I haven't look at gnome-menu's code) it's not using the > gnome-vfs file monitoring api? That sounds shocking :) Something worth poking > upstream about. Haven't checked either; anyway, if we enable inotify, it'd better be enabled in kernel. :P Patch attached.
gnome-menus-2.18.0 also needs the same treatment.
27 Jun 2007; Roy Marples <uberlord@gentoo.org> gnome-menus-2.18.2.ebuild: Only enable inotify if using a Linux kernel.
