X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:subject:from:to:date:in-reply-to
	:references:content-type:mime-version:content-transfer-encoding;
	 q=dns; s=default; b=afoCNFI0jgFo0+N6ytAOk7diTjVttP4K3HZ4tvmM80T
	TkEnnNrWk+NeMgl5xB7BKYEg+a3FJGieTn/aQPVWDp2S2J02nY2gglpU1LilZcZV
	Yv3bvZ43rboZf1HcgGUNoyJTVSP9ejcAxo8WMY6jZ2apRqlkqYuOIPX4XCQqp9Cw
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:subject:from:to:date:in-reply-to
	:references:content-type:mime-version:content-transfer-encoding;
	 s=default; bh=bbg7RaNMLlOwa+fe3g5O5zL+fso=; b=XvI6BY7JUbelpXgVs
	JkyAjOsM+ftu9DMeeEdfX5/iZglvCXFP/IX4BtU9iRi/+194Xjx97oX/Wd4NwJ4B
	VjBaqKcNwlkJaM4YL2jfrnVHIZMK0ioG0m3z3QZRrVbukfh3eLKyzxtvZacWD3cw
	EWSmWfCG8Bh2uYeU6RNkbBse+w=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-0.2 required=5.0 tests=AWL,BAYES_50,KAM_NUMSUBJECT,SPF_HELO_PASS autolearn=no version=3.3.1 spammy=25032019, 25.03.2019, retrieve, H*M:cygwin
X-HELO: mx1.redhat.com
Message-ID: <fa67f31ca3e068ad0e1a8996986ddf9c9c72f3fc.camel@cygwin.com>
Subject: Re: [ANNOUNCEMENT] Updated: mintty 2.9.9
From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Date: Wed, 27 Mar 2019 18:59:08 -0400
In-Reply-To: <fe281b79-3ba1-0352-b73e-ab858d068d30@towo.net>
References: <announce.6264b24c-18bd-814e-16e9-1852f3433e98@towo.net>	 <87pnqq536x.fsf@Rainer.invalid>	 <8bf901a3-5e61-fa65-651f-5bdb9dddba4b@towo.net>	 <20190324181931.GE3471@calimero.vinschen.de>	 <8b43cced-6c22-e9de-046d-0895d0bc4f81@towo.net>	 <87sgvarfgt.fsf@Rainer.invalid>	 <fe281b79-3ba1-0352-b73e-ab858d068d30@towo.net>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.30.5 (3.30.5-1.fc29)
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

On Wed, 2019-03-27 at 21:02 +0100, Thomas Wolff wrote:
> Am 25.03.2019 um 19:12 schrieb Achim Gratz:
> > Thomas Wolff writes:
> > > Sorry, I neither know how to make use of such a package nor how to
> > > generate it or what it contains.
> > > But I'd take a patch:)
> > As you wish…
> I used to use tar rather than cygport package to generate the packages.
> One reason was that I didn’t want my local user/group to appear in them.

They won't show up like that once installed.

> Is that possible with cygport?

Not currently, PTC.

> Trying cygport package, a bunch of problems arise:
> 
> I removed -s as suggested by Achim, added -g as advised by Corinna, but 
> cygport still says:
> *** Info: No debug files, skipping debuginfo subpackage

That's because you are still overriding CFLAGS with := (the first
time).

> Achim also suggested some changes in the cygport file:
> #SRC_URI="https://github.com/${NAME}/release/${NAME}-${VERSION}-src.tar.bz2"
> SRC_URI="https://github.com/${NAME}/${NAME}/archive/${VERSION}.tar.gz"
> → While it’s proper to retrieve the archive (if needed at all; why does 
> cygport refer to this if the package is locally available?) from the 
> release area, and not from the separate “release” repository, 
> unfortunately it’s github URL does not include the “mintty-” prefix 
> (it’s just 2.9.9.tar.gz) which causes the source package generated by 
> cygport to be empty:
>  >>> Creating source package
> /bin/cp: cannot stat '/cygdrive/d/home/mintty/release/2.9.9.tar.gz': No 
> such file or directory
> But apparently it's also sufficient to provide a dummy url:
> SRC_URI="${NAME}-${VERSION}-src.tar.bz2"

The correct value is:

SRC_URI="
https://github.com/${NAME}/${NAME}/archive/${VERSION}/${NAME}-${VERSION}.tar.gz
"

SRC_URI="https://github.com/${NAME}/${NAME}/archive/${VERSION}/${NAME}-${VERSION}.tar.gz"

With your Makefile creating that file name instead of -src.tar.bz2.

> VERSION="2.9.9"
> → This would need the cygport to be generated per version, but 
> apparently it’s not required.
> RELEASE="1"
> → This does not seem to have any effect either.

Only because of how you handle your cygport build, which is *much* more
complicated than it should be.

> Furthermore, cygport complains (on Windows 7 only):
> which: no gdiplus.dll in (...)
> → It’s in $WINDIR/SysWOW64/.

Actually, it's a side-by-side assembly under $WINDIR/WinSxS/ on Win7
x64.  In any case, that can be ignored.

>  >>> mintty requires: bash cygwin
> I remember some discussion that the cygwin dependency, which most 
> packages have, should not (or does not need to be) listed.

That was years ago.  The cygwin dependency can and should be listed
nowadays.

> And in fact, mintty does not depend on bash. Why does cygport think so?

mintheme has a /bin/sh shebang.

> As an alternative, I would accept a description how to generate a debug 
> package "manually", with tar.

Ugly.  Let cygport do this for you.

--
Yaakov



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

