From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: mintty 2.9.9
Date: Wed, 27 Mar 2019 20:02:00 -0000 [thread overview]
Message-ID: <fe281b79-3ba1-0352-b73e-ab858d068d30@towo.net> (raw)
In-Reply-To: <87sgvarfgt.fsf@Rainer.invalid>
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
next prev parent reply other threads:[~2019-03-27 20:02 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-16 9:35 Thomas Wolff
2019-03-16 14:01 ` Achim Gratz
2019-03-24 14:51 ` Steven Penny
2019-03-24 15:57 ` Thomas Wolff
2019-03-24 16:24 ` Brian Inglis
2019-03-24 18:19 ` Corinna Vinschen
2019-03-24 23:36 ` Thomas Wolff
2019-03-25 8:31 ` Corinna Vinschen
2019-03-25 18:12 ` Achim Gratz
2019-03-27 20:02 ` Thomas Wolff [this message]
2019-03-27 20:36 ` Achim Gratz
2019-03-27 21:01 ` Jeffrey Walton
2019-03-27 22:52 ` Steven Penny
2019-03-27 23:09 ` Yaakov Selkowitz
2019-03-28 1:12 ` Steven Penny
2019-03-28 2:35 ` Yaakov Selkowitz
2019-03-28 2:44 ` Brian Inglis
2019-03-28 3:42 ` Steven Penny
2019-03-28 7:34 ` Thomas Wolff
2019-03-28 11:36 ` Steven Penny
2019-03-28 15:09 ` Brian Inglis
2019-03-28 18:22 ` Dependancy Hell (was Re: [ANNOUNCEMENT] Updated: mintty 2.9.9) Chris Wagner
2019-03-28 17:37 ` [ANNOUNCEMENT] Updated: mintty 2.9.9 Achim Gratz
2019-03-27 22:59 ` Yaakov Selkowitz
2019-03-28 7:15 ` Björn Stabel
2019-03-28 17:40 ` Achim Gratz
2019-03-28 18:08 ` Thomas Wolff
2019-03-28 18:21 ` Achim Gratz
2019-03-28 18:32 ` Thomas Wolff
2019-03-28 19:47 ` Achim Gratz
2019-03-28 21:38 ` Thomas Wolff
2019-03-28 8:43 ` Thomas Wolff
2019-03-28 9:36 ` Corinna Vinschen
2019-03-28 14:02 ` Jeffrey Walton
2019-03-28 18:10 ` Thomas Wolff
2019-03-28 18:16 ` Vince Rice
2019-03-28 18:33 ` Thomas Wolff
2019-03-28 18:43 ` Vince Rice
2019-03-28 21:34 ` Thomas Wolff
2019-03-28 22:28 ` Steven Penny
2019-03-24 21:05 ` Andrey Repin
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fe281b79-3ba1-0352-b73e-ab858d068d30@towo.net \
--to=towo@towo.net \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).