From owner-freebsd-ports@freebsd.org Thu Jan 7 14:40:51 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7A8BAA65038 for ; Thu, 7 Jan 2016 14:40:51 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3DE061AE9 for ; Thu, 7 Jan 2016 14:40:51 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 2198820B83 for ; Thu, 7 Jan 2016 09:40:50 -0500 (EST) Received: from web6 ([10.202.2.216]) by compute5.internal (MEProxy); Thu, 07 Jan 2016 09:40:50 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=L0kqZlj6bHCKYFd 4JtqB19caADs=; b=gL6Ns/vdCyRY8teELNEEjWerUC4RgtRDhNNAbfSDNvOUXPh pLXt0rpzVPMB3jwFaPm7zURFs6Ab21B5YcBG9fnrE/2P85eZHhG4gtiFvTUI4sDn heq3yYzvafxdse+yYK/NUEhfwBUls0bQB9eZISUALTSSuR1acZ/LifZv2MMU= Received: by web6.nyi.internal (Postfix, from userid 99) id F13F34DAF4; Thu, 7 Jan 2016 09:40:49 -0500 (EST) Message-Id: <1452177649.2464154.485516546.12D50CC8@webmail.messagingengine.com> X-Sasl-Enc: xuzHgFuGYjtkwP4AesMuwIDO5YMCqOnMRqlAVQHw+6fJ 1452177649 From: Mark Felder To: Matthew Seaman , freebsd-ports@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-6cda141f In-Reply-To: <1452176770.2461098.485503778.2BE41C35@webmail.messagingengine.com> References: <567D18B6.4010702@peercorpstrust.org> <448u4epe3z.fsf@be-well.ilk.org> <1451929436.1527959.482548682.05032107@webmail.messagingengine.com> <20160104233032.213abbc07e7055f3cf8d53ca@gmail.com> <568E06A5.2060303@peercorpstrust.org> <568E3B8C.8010107@freebsd.org> <1452176770.2461098.485503778.2BE41C35@webmail.messagingengine.com> Subject: Re: Porting Catfish and Autokey to FreeBSD Date: Thu, 07 Jan 2016 08:40:49 -0600 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jan 2016 14:40:51 -0000 On Thu, Jan 7, 2016, at 08:26, Mark Felder wrote: > > > On Thu, Jan 7, 2016, at 04:18, Matthew Seaman wrote: > > On 01/07/16 06:33, PeerCorps Trust Fund wrote: > > > It seems as though FreeBSD has an inotify compatibility layer. > > > > > > At least that's what we've been informed. One committer in the > > > community is currently working on getting it operational and into the > > > ports collection. > > > > It's already been ported. See devel/libinotify > > > > I say 'ported' but this is a wrapper providing the inotify API built on > > top of kqueue(2), because FreeBSD doesn't provide the same notification > > kernel functions as Linux does. > > > > This implementation passes the inotify test suite and as far as I can > > tell, behaves almost identically, except for the semantics around > > process fork(2)'ing. Under Linux, you can set up inotify and have those > > settings preserved in a child process after forking. kqueue(2) doesn't > > let you do that. > > > > Upstream has rejected a pull request to add FreeBSD support to pyinotify > via libinotify due to their inability to guarantee it will work right > > https://github.com/seb-m/pyinotify/pull/64 > Oh I see now jpaetzel is engaging them about this. Perhaps this is who you were talking to? -- Mark Felder ports-secteam member feld@FreeBSD.org