public inbox for
 help / color / mirror / Atom feed
From: Mark Geisert <>
To: Cygwin-Apps <>
Subject: Re: [ITP] cygfuse -- cygport issues solved
Date: Sun, 27 Mar 2022 01:20:27 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Mark Geisert wrote:
> Hi Jon,
> Thanks for the helpful review comments.

cygport is a wondrous tool.  My issues were solved by making a simple tar.xz of my 
local source tree, renaming it to have the version number expected by the cygport 
script, placing that file and the cygport script in a test directory, then running 
'cygport cygfuse.cygport prep'.  All the necessary subdirectories are then built 
and the build, install, package steps run correctly.  Next is upload and announce.

I was making things more complicated than they needed to be.
cygport is a wondrous tool.  Thanks Yaakov!


      reply	other threads:[~2022-03-27  8:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10  6:16 [ITP] cygfuse Mark Geisert
2022-03-10 20:53 ` Marco Atzeri
2022-03-12 14:43 ` Jon Turney
2022-03-12 14:46   ` Jon Turney
2022-03-25  8:24   ` Mark Geisert
2022-03-27  8:20     ` Mark Geisert [this message]

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