DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=t0BjGOLDX8FM6fUr
	gKLjwo0loGSFiGMiiZBv1PQDt8Y24U5yQc11r1umz6eiTanVVVoBAwhmZ/SvMn0A
	lv0sXaaDEMpMIQTjnDF9qIGhpeeh16k3970FsGQmhhs2Pf8pptZ7iAJgdQXnKOGR
	QT7LeiIE9rpP0sWvflzA/jbjHCE=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: mintty 2.9.9
To: cygwin@cygwin.com
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>
From: Thomas Wolff <towo@towo.net>
Message-ID: <fe281b79-3ba1-0352-b73e-ab858d068d30@towo.net>
Date: Wed, 27 Mar 2019 21:02:47 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <87sgvarfgt.fsf@Rainer.invalid>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

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.
Is that possible with cygport?

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

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"

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.

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

 >>> 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.
And in fact, mintty does not depend on bash. Why does cygport think so?

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

Thomas

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