This is the mail archive of the
mailing list for the Cygwin project.
Re: [ANNOUNCEMENT] Updated: mintty 2.9.9
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:
→ 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:
→ This would need the cygport to be generated per version, but
apparently it’s not required.
→ 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.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple