X-Recipient: archive-cygwin AT delorie DOT 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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=S0ovyrbdXlipcjk1py+GRrCKz4uM34SaPaTbYfUYdIQ3SBnU/ZUKc
	AE2QEkzHKPVNWrPsluHKgZopOzw5J0B7jLNlH7cdxUb937tFdVqEtWZBJd35ouWi
	RclHU5kqQAH+gkhlRERkr9hYJG7HkE37RISspQptfbHTYG8uVv6HgM=
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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=jeSGAXy+4beJSqoK3ZpWGL0WeVI=; b=Z4c8TfChs+Z73klT8Qr74iVJ52PY
	9AGyb6z+433ZfsrFHmWbAoIYvJmWLpfhO0qi46gvKjWKkEl42dYPpom8+i0UpxRU
	7Gpkljf0Ntbre3Rh/RVuMQ0P5DmKlgmcDuFYFUd5QpdpvTPFaSnN1hXAMJXhBrhr
	d0EH5mGh0sFCjIo=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-103.6 required=5.0 tests=AWL,BAYES_50,GOOD_FROM_CORINNA_CYGWIN,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy=retrieve, Gratz, gratz, helpfully
X-HELO: mout.kundenserver.de
Date: Thu, 28 Mar 2019 10:36:36 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] Updated: mintty 2.9.9
Message-ID: <20190328093636.GO4096@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <announce DOT 6264b24c-18bd-814e-16e9-1852f3433e98 AT towo DOT net> <87pnqq536x DOT fsf AT Rainer DOT invalid> <8bf901a3-5e61-fa65-651f-5bdb9dddba4b AT towo DOT net> <20190324181931 DOT GE3471 AT calimero DOT vinschen DOT de> <8b43cced-6c22-e9de-046d-0895d0bc4f81 AT towo DOT net> <87sgvarfgt DOT fsf AT Rainer DOT invalid> <fe281b79-3ba1-0352-b73e-ab858d068d30 AT towo DOT net> <fa67f31ca3e068ad0e1a8996986ddf9c9c72f3fc DOT camel AT cygwin DOT com> <f8600ba7-08cd-3551-6f57-1517ae84f4f8 AT towo DOT net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="45wMVEkw4XUbiYON"
Content-Disposition: inline
In-Reply-To: <f8600ba7-08cd-3551-6f57-1517ae84f4f8@towo.net>
User-Agent: Mutt/1.11.3 (2019-02-01)

--45wMVEkw4XUbiYON
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mar 28 09:43, Thomas Wolff wrote:
> Achim Gratz wrote:
> >=20
> > > Trying cygport package, a bunch of problems arise:
> > >=20
> > > I removed -s as suggested by Achim, added -g as advised by Corinna,
> > > but cygport still says:
> > > *** Info: No debug files, skipping debuginfo subpackage
> > Well, do not reset CFLAGS in your Makefile and cygport helpfully
> > provides all the scaffolding you need.  You might have noticed I
> > replaced the ":=3D" in your Makefile for exactly that reason.
> I wondered why and forgot... Works now, thank you.
> > A build system is supposed to be able to pre-configure CFLAGS without y=
our
> > Makefile nixing all of that effort.
> As also indicated by Jeffrey Walton. However, I'll do only minimal revisi=
on
> of the Makefile, as required.
>=20
> >=20
> > > Achim also suggested some changes in the cygport file:
> > > #SRC_URI=3D"https://github.com/${NAME}/release/${NAME}-${VERSION}-src=
.tar.bz2"
> > > SRC_URI=3D"https://github.com/${NAME}/${NAME}/archive/${VERSION}.tar.=
gz"
> > > =E2=86=92 While it=E2=80=99s proper to retrieve the archive (if neede=
d at all; why
> > > does cygport refer to this if the package is locally available?)
> > It's generally considered bad form to provide a cygport file that
> > doesn't work standalone and the SRC_URI you provided only got me a 404.
> Referring to the "release" repository was only a fallback rescue setting,
> because due to github's strange URL scheme, the working download URL would
> confuse cygport.

If your repo is on github anyway it would be much simpler to define
the source as a git repo.  Rather than SRC_URI, just use something
like this:

GIT_URI=3D"https://github.com/mintty/mintty.git" # Just as example
# Either...
GIT_TAG=3D"your release tag"
# ...or...
GIT_REV=3D"matching sha1-hash"
inherit git

> Sure, that's why the VERSION should better not be mentioned in it, right?

No, the VERSION and RELEASE fields define how tohe package is called
when you do `cygport package'.

Did you read Cygwin's Package Contributor's Guide?

https://cygwin.com/packaging-contributors-guide.html

It's really not that complicated to do it right.


Corinna

--=20
Corinna Vinschen
Cygwin Maintainer

--45wMVEkw4XUbiYON
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAlyclaQACgkQ9TYGna5E
T6B8SRAAgfWpJfBZ+aOOF2iypT70L3uktBRUaFC5oghlzqa22EBC7zLefbywLYJi
NP3vcEFPAnjED2452CAQF7eiOxJS/YYB5wVDkjLtZXDtaSLG9eTqq7PGfxctsuxe
V6iwa2RyKCz/2I+Jm6sutv0u9WAOgx33PU+tj30401wIQoGOiwhIhSotL2spkCa+
sazvlrnMkdoxxZs+gAMbEuAK5JblEs3eEXOnWa8U8gvEUSJZ30sDIoDp4LU+X7Pf
GrkAxsW99qpL58E5EzPgL/+BA7JzViGMoJ3h1ux4uOWJtvV3SNs6o4oG7i3wPW8y
yZIBTfpRat46Q/NMVQxNuC2SZ1XiFU4+JFBpFL9sBxJiuIMNN6ox2UWKomx2FGOx
9lKPVZFh/QVwAw2XwDHRfsc0VIa1PTRAtiXyP154PeAGXf2GgJgxgSSCvHhOI4vY
irjudDHgmjFHZqtlQUYrxqCxO9h5fuq3dhNhiAOZxaOC6mgLUZRa7dQ7nbedDI3a
RcEzszJvmD2Ey54eaeOSFyITsmR7C0o0J4FR+sGJMZgStOj0dDv1/XwvkkVwQxyq
CIVYTUPZzHJhENVA6D5jhGIVKkenCo8wLzSlQvOnWh+s8iQ6pdDCghRF7Cl7OX/n
hVJ30Xdb1adb7uvQuYw9cj46r/HniLUxdx8zToWuX7ezPgypow4=
=GBQ6
-----END PGP SIGNATURE-----

--45wMVEkw4XUbiYON--