public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Samuli Suominen <ssuominen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Make inotify a global USE flag?
Date: Thu, 21 Mar 2013 12:32:31 +0200	[thread overview]
Message-ID: <514AE1BF.3030605@gentoo.org> (raw)
In-Reply-To: <20810.57629.196394.526922@a1i15.kph.uni-mainz.de>

On 21/03/13 12:29, Ulrich Mueller wrote:
> These packages have inotify as local USE flag:
>
>     app-editors/emacs-vcs
>     app-misc/recoll
>     app-misc/strigi
>     dev-libs/ecore
>     dev-vcs/git-annex
>     media-sound/mpd
>     net-im/ekg2
>     net-misc/mediatomb
>     sys-fs/aufs2
>     sys-fs/aufs3
>     sys-process/cronie
>
> Should we make it a global flag? What description is better:
>
>     inotify - Enable inotify filesystem monitoring support
>     inotify - Enable inotify file change notification support

+1, ...

... despite that most of these shouldn't even have a USE flag for 
inotify, instead it should always be enabled with 'kernel_linux' and let 
the application itself do a runtime check if inotify is available or not
since these have no external dependencies (other than virtual/os-headers)
not everything should be put behind USE flag :-/

- Samuli


  reply	other threads:[~2013-03-21 10:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-21 10:29 [gentoo-dev] Make inotify a global USE flag? Ulrich Mueller
2013-03-21 10:32 ` Samuli Suominen [this message]
2013-03-21 11:43   ` Peter Stuge
2013-03-21 12:02     ` Samuli Suominen
2013-03-21 12:10       ` Peter Stuge
2013-03-21 12:19         ` Sergey Popov
2013-03-21 12:26         ` Samuli Suominen
2013-03-21 13:33           ` Peter Stuge
2013-03-21 14:30             ` Tom Wijsman
2013-03-21 16:32   ` Michał Górny
2013-03-21 11:48 ` Alexander Berntsen
2013-03-21 14:14   ` Ulrich Mueller
2013-03-21 16:14     ` Alexander Berntsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=514AE1BF.3030605@gentoo.org \
    --to=ssuominen@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox