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=eN9I1Qoc/r1WIHiKh+zZgSYka97y7AvmMisU0zHS4/HmdEBED/fva
	7oNm+xRy+rguSDBBmGgdLoqWcmWNKLKa7tFtCGRYbqe6J0Vt+z2TKduqd1YsIRWD
	o6U8jO+eK/F7Xvs/RSC4s3XPeJwng5O5+fTQ+zf8QufYp8mylGh2L8=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Wed, 8 Oct 2014 18:37:25 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Packages up for adoption
Message-ID: <20141008163725.GH29235@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <CAGHJv4dmKs=USE51uj3vL8dDDsFNV7cUzHLuFQKKNVzg6SerBQ AT mail DOT gmail DOT com> <541C4417 DOT 40806 AT etr-usa DOT com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;	protocol="application/pgp-signature"; boundary="PNpeiK4tTqhYOExY"
Content-Disposition: inline
In-Reply-To: <541C4417.40806@etr-usa.com>
User-Agent: Mutt/1.5.23 (2014-03-12)

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

Hi Warren,

On Sep 19 08:56, Warren Young wrote:
> On 9/18/2014 11:44, Chris Sutcliffe wrote:
> >
> >I'm looking for any volunteers to take over
> >maintainership of the following packages: mksh
>=20
> I'm also somewhat interested in this one.  I've never been a Korn shell
> user, but I recently learned about mksh and its place in Bourne family sh=
ell
> history. [1]  Only a ksh93 package would be more valuable, but until some=
one
> adopts that, I think mksh still has a place in Cygwin.
>=20
> More questions:
>=20
> 1. Where is the source package?  setup.exe doesn't offer it.

It's definitely available on cygwin.com, and it's also mentioned in
setup.ini.

> 2. Have you cygported it yet?  I built it from the official tarball, and
> while it has a primitive non-Autotools build system, it looks compatible
> with cygport.

Yes, Chris cygported it already.

> 3. Other than time, is there a reason you haven't released R50b yet?  It
> seems to pass its own test suite here, so if I adopt it, I'm committing to
> releasing R50b shortly, unless there are traps I haven't discovered.
>=20
> 4. What do you think about replacing mksh in Cygwin with ksh93?  It seems
> OSS-enough to make Red Hat happy. [2]

ksh93 comes with a compatibility layer lib called AST.  I don't think
this lib has ever been ported to Cygwin 1.7.  The last official binary
release for Cygwin is for 32 bit only, dated 2012-08-06.  From the
README files in the sources I gather the latest Cygwin patch is from
2004, which is way back in the Cygwin 1.5 era.  A quick scan of the
latest released source shows that AST still uses the pre-1.7 path
conversion functions which are not available on 64 bit Cygwin.  There's
a bit of porting required I guess.


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--PNpeiK4tTqhYOExY
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJUNWhFAAoJEPU2Bp2uRE+gPpYQAI+AXwwZ/3Gwzz9njXJ8G8Ee
NopIlfuuN3Ouj0ITWCy5WrN/fxsA3s42qNhW95WaLShCUU96WK92PAVOHpxJFwwD
L4ioEkSm6PCavoNJcsacIw/QRtYyxW/9sqttnpoPzYOn539Md7/HLRhdF/H+zRj+
NnOGq7P7lVsfb3DZutk6vLHcNaFXe1lZcTlOgigDCf5I+OU5CfdwUTZK8zlGiX7p
xj7SvGi8wqYAUpmDdzYLwkPInRcE9IkubDhhwPF/nm88NZz5SEIMrNmdJiApTVL7
WfuBrqHgUIfbz6zG7qJucYBsk+4yqKskkKHDoafYd0LMfAv/4KLMEyNZlWxQQrtt
scNd7YGoq8qcbBmat264Kaw883INPEM20oO0zz2p8FbCmKnbUSE0UoTysKenZkp1
U7TgoLIHzsI97JO/iQF8fp0iEaZJVGIfNOxXrFJ67/M0UcjbQqw5fbgw6zmEaYXx
8YoVE3CWXRZT6JKxyGvws9xKGajRlmxs+qsDudGB1rlSzkRIAZQ1FtHxsWXi5o/D
SBaBMM20GWN9BuF7Q5ezttw0I4IWoKusGNiphD4FNEFfPMOCQsnmV7QCXdGD3/Ch
gDNr6ugXcu8+L40SU46sfiaQuDX53bpsimu0JrJn99S2Zwt2XNZi9H3Ny9A/qgxF
i2CD0nn4ebly3s6fOKMq
=dIW4
-----END PGP SIGNATURE-----

--PNpeiK4tTqhYOExY--