On Fri, Sep 28, 2018 at 11:53:48AM +0200, Antoine Jacoutot wrote:
> On Thu, Sep 27, 2018 at 04:52:45PM +0300, Paul Irofti wrote:
> > On 9/27/2018 4:31 PM, Landry Breuil wrote:
> > > On Thu, Sep 27, 2018 at 03:50:16PM +0300, Paul Irofti wrote:
> > > > Hi,
> > > >
> > > > Why isn't libinotify installed in /usr/local/lib?
> > > >
> > > > CONFIGURE_ARGS = --libdir=${PREFIX}/lib/inotify/ \
> > > > --includedir=${PREFIX}/include/inotify/
> > > >
> > > > This choice implies path manipulation and patching for most ports that
> > > > depend on it.
> > >
> > > Because it's an evil linux only thing that half works on openbsd through
> > > broken kqueue implementation, so nobody wants it to be silently picked
> > > by potential users..
> > >
> > > Landry
> > >
> >
> > Ah, our famous NIH syndrome! Got it!
>
> No it's not like that at all.
> It's the kqueue implementation in it that is half broken and unmaintained (and
> that was written for BSD, so definitely *not* NIH). If someone can have a look
> at it and make sure it's working fine, then we can open the usage to a broader
> amount of ports.
I see, that makes more sense I guess. Thanks!
Sorry, maybe I was a bit exaggerated with my NIH comment.
"Evil linux only" seems to be replacing the "Evil Windows only" 2000's
phrase, that is not a valid logical argument and always triggered me :)
