The current recoll-1.17.3-r1 ebuild has gone back to requiring fam or inotify, neither of which are essential. Bug 389595 fixed this for 1.16, but apparently its back. Trying to emerge recoll, I get: tuppence ~ # USE="-fam -inotify" emerge -pv recoll These are the packages that would be merged, in order: Calculating dependencies \ !!! Problem resolving dependencies for app-misc/recoll ... done! !!! The ebuild selected to satisfy "recoll" has unmet requirements. - app-misc/recoll-1.17.3-r1::gentoo USE="camelcase chm dvi exif ics info pdf postscript qt4 rtf spell tex xattr xml -audio -djvu -fam -inotify -lyx -msdoc -msppt -msxls -session -wordperfect" The following REQUIRED_USE flag constraints are unsatisfied: exactly-one-of ( fam inotify ) The above constraints are a subset of the following complete expression: exactly-one-of ( fam inotify ) session? ( any-of ( fam inotify ) ) tuppence ~ # Reproducible: Always Steps to Reproduce: 1. Try to emerge recoll 2. 3. Actual Results: See above Expected Results: Recoll emerging without fam or inotify.
Why do you need INOTIFY disabled? I think that should be enabled for default for Linux and the USE=fam should be masked everywhere except in BSD profiles
(In reply to comment #1) > Why do you need INOTIFY disabled? I think that should be enabled for default > for Linux and the USE=fam should be masked everywhere except in BSD profiles I have a related problem: if I am correct, fam is enabled by default in /usr/portage/profiles/targets/desktop/make.defaults. No problem about that, but if you look at /usr/portage/app-misc/recoll/recoll-1.17.3-r1.ebuild, you will find that: IUSE="+spell +inotify +qt4 +session camelcase xattr fam ${INDEX_HELPERS}" Which means that inotify is also enabled by default (if I understand correctly). This is a bit contradictory because it means that one of the two has to be disabled by the user.
+*recoll-1.18.1 (30 Jan 2013) + + 30 Jan 2013; Markos Chandras <hwoarang@gentoo.org> +recoll-1.18.1.ebuild: + Version bump #454554. Don't require inotify or fam. Bug #452192 +
