Re: [ANNOUNCEMENT] Updated: mintty 2.9.9

[Corinna Vinschen <corinna-cygwin at cygwin dot com>]

On Mar 25 00:36, Thomas Wolff wrote:
> Hi Corinna,
> 
> Am 24.03.2019 um 19:19 schrieb Corinna Vinschen:
> > On Mar 24 16:57, Thomas Wolff wrote:
> > > Hi Achim,
> > > 
> > > Am 16.03.2019 um 15:00 schrieb Achim Gratz:
> > > > Thomas Wolff writes:
> > > > > I have uploaded mintty 2.9.9 with the following changes:
> > > > While you're at it, could you please stop using the release number "0" for your packages?
> > > I had previously explained why I used to like this (native package, no
> > > patches) and there had been no comments...
> > > > That's supposed to be used for test packages only
> > > > (if you want to make an effort to convey that in the package file name).
> > > I don't see this documented anywhere.
> > > > Proper releases should start with "1".
> > > > 
> > > > https://cygwin.com/packaging-contributors-guide.html#updating
> > > OK, I see *this* described now; I think it changed some time. Was there any
> > > discussion about it?
> > > Anyway, with maybe one more vote, I'll make the change.
> > While you're at it, a mintty-debuginfo package may be pretty helpful.
> Sorry, I neither know how to make use of such a package nor how to generate
> it or what it contains.

It's autogenerated if you compile and link with -g and refrain from
stripping your executables with -s.  Cygport checks by itself if
debug symbols are available, moves them to /usr/lib/debug and
strips your executable afterwards.


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer

Attachment: signature.asc
Description: PGP signature