| 1 |
On 21/03/13 12:29, Ulrich Mueller wrote: |
| 2 |
> These packages have inotify as local USE flag: |
| 3 |
> |
| 4 |
> app-editors/emacs-vcs |
| 5 |
> app-misc/recoll |
| 6 |
> app-misc/strigi |
| 7 |
> dev-libs/ecore |
| 8 |
> dev-vcs/git-annex |
| 9 |
> media-sound/mpd |
| 10 |
> net-im/ekg2 |
| 11 |
> net-misc/mediatomb |
| 12 |
> sys-fs/aufs2 |
| 13 |
> sys-fs/aufs3 |
| 14 |
> sys-process/cronie |
| 15 |
> |
| 16 |
> Should we make it a global flag? What description is better: |
| 17 |
> |
| 18 |
> inotify - Enable inotify filesystem monitoring support |
| 19 |
> inotify - Enable inotify file change notification support |
| 20 |
|
| 21 |
+1, ... |
| 22 |
|
| 23 |
... despite that most of these shouldn't even have a USE flag for |
| 24 |
inotify, instead it should always be enabled with 'kernel_linux' and let |
| 25 |
the application itself do a runtime check if inotify is available or not |
| 26 |
since these have no external dependencies (other than virtual/os-headers) |
| 27 |
not everything should be put behind USE flag :-/ |
| 28 |
|
| 29 |
- Samuli |
Archives