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

Hi Jon,
Thanks for the helpful review comments. More below.

Jon Turney wrote:
> On 10/03/2022 06:16, Mark Geisert wrote:
[...]> A few small comments on the cygport file
>> #SRC_URI="${PV}.tar.xz" 
>> #NOT YET:    inherit git
> It's unclear where the upstream source tarball comes from...

Things were in flux and are now straightened out. There's just a SRC_URI now.
>> # take over these activities from cygport..
> This should be written 'RESTRICT=strip', I think.

Yep, thanks.

>> src_compile()
>> {
>>     # fix source tree glitch.. (maybe 'prep' stumbling or bad tarfile layout?)
>>     if [ -e ${S}/src ]; then
>>     mv ${S}/src/cygfuse ${S}
>>     rmdir ${S}/src
>>     fi
> I think this can be handled with 'SRC_DIR=src/cygfuse' (and suitable adjustment to 
> paths throughout)

I had tried several variations on this before the initial ITP post. I tried again 
after your comment. I'm still having issues with source layout.

I think my trouble is I'm bootstrapping my own source tree and there seem to be 
conventions (that I don't know) on how it should be laid out. It seems the source 
tarball generated by cygport doesn't match the layout of my own source tree.

Should my original source be in directory "src" or "src/cygfuse"? If the latter, 
should there be a version number as part of the directory name? Should my original 
source be placed under "origsrc" or "src"? These questions pertain to layout 
before cygport is run to generate the first-ever package tarballs.

Currently the build, install, package steps seem to run to completion.  But doing 
a fetch and prep of the tarball has got me stymied (in the prep step).  Error is
     SRC_DIR is not correctly defined
I have been perusing /usr/share/cygport/*.cygpart but haven't found a solution.


  parent reply	other threads:[~2022-03-25  8:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10  6:16 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 [this message]
2022-03-27  8:20     ` [ITP] cygfuse -- cygport issues solved 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).