From: ASSI <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: fuse
Date: Tue, 01 Feb 2022 07:20:24 +0100 [thread overview]
Message-ID: <87wnif5crb.fsf@Otto.invalid> (raw)
In-Reply-To: <7d9cc328-2af9-6171-6407-80e9d7fdcdc8@maxrnd.com> (Mark Geisert's message of "Mon, 31 Jan 2022 19:50:34 -0800")
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.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2022-02-01 6:20 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 ` ASSI [this message]
2022-04-13 19:55 ` fuse Jon Turney
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=87wnif5crb.fsf@Otto.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin-apps@cygwin.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).