From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>,
Mark Geisert <mark@maxrnd.com>
Subject: Re: fuse
Date: Wed, 13 Apr 2022 20:55:49 +0100 [thread overview]
Message-ID: <4f182ee9-a210-6131-f17a-eb7c1a9d0e4b@dronecode.org.uk> (raw)
In-Reply-To: <87wnif5crb.fsf@Otto.invalid>
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
next prev parent reply other threads:[~2022-04-13 19:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 22:45 fuse Thomas Wolff
2022-01-10 6:00 ` fuse Mark Geisert
2022-02-01 3:50 ` fuse Mark Geisert
2022-02-01 6:20 ` fuse ASSI
2022-04-13 19:55 ` Jon Turney [this message]
2022-04-15 8:11 ` fuse Mark Geisert
2022-02-04 6:58 ` fuse Mark Geisert
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=4f182ee9-a210-6131-f17a-eb7c1a9d0e4b@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
--cc=mark@maxrnd.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).