public inbox for
 help / color / mirror / Atom feed
From: Mark Geisert <>
To: Cygwin-Apps <>
Subject: Re: fuse
Date: Fri, 15 Apr 2022 01:11:38 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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]

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.


  reply	other threads:[~2022-04-15  8:11 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       ` fuse Jon Turney
2022-04-15  8:11         ` Mark Geisert [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).