From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from m0.truegem.net (m0.truegem.net [69.55.228.47]) by sourceware.org (Postfix) with ESMTPS id CA12F385843E for ; Fri, 15 Apr 2022 08:11:43 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org CA12F385843E Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=maxrnd.com Authentication-Results: sourceware.org; spf=none smtp.mailfrom=maxrnd.com Received: (from daemon@localhost) by m0.truegem.net (8.12.11/8.12.11) id 23F8BeG8095778 for ; Fri, 15 Apr 2022 01:11:40 -0700 (PDT) (envelope-from mark@maxrnd.com) Received: from 162-235-43-67.lightspeed.irvnca.sbcglobal.net(162.235.43.67), claiming to be "[192.168.1.100]" via SMTP by m0.truegem.net, id smtpdbIIc5k; Fri Apr 15 01:11:38 2022 Subject: Re: fuse To: Cygwin-Apps References: <7d9cc328-2af9-6171-6407-80e9d7fdcdc8@maxrnd.com> <87wnif5crb.fsf@Otto.invalid> <4f182ee9-a210-6131-f17a-eb7c1a9d0e4b@dronecode.org.uk> From: Mark Geisert Message-ID: <9fcb3c89-347c-2ec8-a9f5-00b658c5289d@maxrnd.com> Date: Fri, 15 Apr 2022 01:11:38 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.4 MIME-Version: 1.0 In-Reply-To: <4f182ee9-a210-6131-f17a-eb7c1a9d0e4b@dronecode.org.uk> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-4.5 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, SPF_HELO_NONE, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin-apps@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Cygwin package maintainer discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Apr 2022 08:11:47 -0000 Hi Jon, Achim, Jon Turney wrote: > On 01/02/2022 06:20, ASSI wrote: >> Mark Geisert writes: >>> I see that 'mtr' is another Cygwin package that makes use of a Windows >>> driver via libpcap.  Maybe I can use mtr.cygport etc as a guide; I'm >>> unsure whether a Cygwin package should be including Windows drivers. >> >> No they should not, although there is at least one other package (libusb >> IIRC) that requires non-standard Windows drivers for functioning fully >> or correctly.  How to present that requirement in setup is another >> question. > > The 'message:' line in the .hint file (see [1]) can be used for a related purpose > of telling people that Windows drivers are needed, although in fact this is only > used by libusb0 at the moment. > > Actually checking for those being installed generically in setup seems fraught. > But I guess you could write a postinstall script which checks somehow for it's > presence and fails if it's not present? > > [1] https://cygwin.com/packaging-hint-files.html I had seen "message:" there on [1] and tried once to make use of it, but failed. From reading cygport's pkg_pkg.cygpart, it seemed to me that a 'MESSAGE="foo"' line in the cygfuse.cygport file should cause a 'message: cygfuse "foo"' to be emitted to the .hint file. That didn't seem to happen. Maybe I goofed. I then thought about manually adding the "message: ..." line, but then realized I had two full 75-char lines of info to display and did not know if that was too big or what it would look like. I dropped the idea for the time being and went with an Overview section on the package update announcement instead. I should look at libusb.cygport; thanks Achim for that reminder. Regards, ..mark