| 1 |
On Thu, 21 Mar 2013 12:32:31 +0200 |
| 2 |
Samuli Suominen <ssuominen@g.o> wrote: |
| 3 |
|
| 4 |
> On 21/03/13 12:29, Ulrich Mueller wrote: |
| 5 |
> > These packages have inotify as local USE flag: |
| 6 |
> > |
| 7 |
> > app-editors/emacs-vcs |
| 8 |
> > app-misc/recoll |
| 9 |
> > app-misc/strigi |
| 10 |
> > dev-libs/ecore |
| 11 |
> > dev-vcs/git-annex |
| 12 |
> > media-sound/mpd |
| 13 |
> > net-im/ekg2 |
| 14 |
> > net-misc/mediatomb |
| 15 |
> > sys-fs/aufs2 |
| 16 |
> > sys-fs/aufs3 |
| 17 |
> > sys-process/cronie |
| 18 |
> > |
| 19 |
> > Should we make it a global flag? What description is better: |
| 20 |
> > |
| 21 |
> > inotify - Enable inotify filesystem monitoring support |
| 22 |
> > inotify - Enable inotify file change notification support |
| 23 |
> |
| 24 |
> +1, ... |
| 25 |
> |
| 26 |
> ... despite that most of these shouldn't even have a USE flag for |
| 27 |
> inotify, instead it should always be enabled with 'kernel_linux' and let |
| 28 |
> the application itself do a runtime check if inotify is available or not |
| 29 |
> since these have no external dependencies (other than virtual/os-headers) |
| 30 |
> not everything should be put behind USE flag :-/ |
| 31 |
|
| 32 |
net-im/ekg2 fixed. But you should seriously consider opening a bug, at |
| 33 |
least a common one CC-ing all the remaining maintainers. |
| 34 |
|
| 35 |
|
| 36 |
-- |
| 37 |
Best regards, |
| 38 |
Michał Górny |
Archives