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=IMMInX0WggfxffKc/hlPuH8SXQE8ByM/rq8RiqLqxXDY/VdvqwRXC
	IfquD+pQM/uCWJ5sTQzuEhOh3Pdw/6Usqf1Mme0NmnUDWIqCPAQ2Q+seoqvGspjR
	OTe5EOMP52OkW9zORsGocw2Y3wDU+uqFqwEoMl0G4fpLUfTjD10T6w=
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=TlNbwG+CK1ddBhXJX5dpErDNHv4=; b=ovi72XtFDzOcM/CLve0EmXm+zNNy
	ADqyvtfuSUuiHCwjgTjPxZSX10qjGeQIFQS9vazlxjZmW+sWYpqa/dmgq1PRsGyI
	iQVdfe5xJVVBR04xmwnFtBqoI4wYCrgFbZDBGQPKpF9GoIPN9ihN1pmHNjXD89+s
	faCjkmCHefGSA+8=
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-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-93.4 required=5.0 tests=AWL,BAYES_05,KAM_LAZY_DOMAIN_SECURITY,KHOP_DYNAMIC,RCVD_IN_BRBL_LASTEXT,RCVD_IN_PBL,RDNS_DYNAMIC,USER_IN_WHITELIST autolearn=no version=3.3.2 spammy=H*i:sk:56A5244, H*MI:sk:56A5244, H*f:sk:56A5244, Hx-languages-length:2208
X-HELO:	calimero.vinschen.de
Date:	Sun, 24 Jan 2016 23:57:44 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.5.0-0.1
Message-ID:	<20160124225744.GC27138@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<announce DOT 20160124115654 DOT GB11514 AT calimero DOT vinschen DOT de> <56A52443 DOT 7030809 AT cornell DOT edu>
MIME-Version:	1.0
In-Reply-To:	<56A52443.7030809@cornell.edu>
User-Agent:	Mutt/1.5.24 (2015-08-30)

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

Hi Ken,

On Jan 24 14:21, Ken Brown wrote:
> On 1/24/2016 6:56 AM, Corinna Vinschen wrote:
> >Hi Cygwin friends and users,
> >
> >
> >I released a new Cygwin TEST version 2.5.0-0.1.
> >
> >This release introduces a major change addressing developers only, so
> >as a user you can skip this test release.
> >
> >tl;dr: Cygwin 2.5.0 switches Cygwin from the Solaris ACL API to the
> >        POSIX.1e ACL API.
> > [...]
> >Please give this new POSIX.1e ACL implementation a test.  If you have
> >a project or maintain a package utilizing ACLs, please make sure that
> >your project picks up the new POSIX.1e API and that it works as desired.
> >
> >Projects like emacs, vim, coreutils come to mind...
>=20
> Hi Corinna,
>=20
> emacs builds and passes its test suite.  Here are the configure results
> related to ACLs:
>=20
> TESTS FOR FUNCTIONS
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Yes:
>=20
> acl_delete_def_file
> acl_entries
> acl_extended_file
> acl_free
> acl_from_mode
> acl_from_text
> acl_get_fd
> acl_get_file
> acl_set_fd
> acl_set_file
>=20
> No:
>=20
> acl_copy_ext_native
> acl_create_entry_np
> acl_delete_fd_np
> acl_delete_file_np
> acl_free_text
> acl_to_short_text
>=20
> TESTS FOR HEADERS
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Yes:
>=20
> <acl/libacl.h>
> <sys/acl.h>
>=20
> OTHER TESTS
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> constant ACL_FIRST_ENTRY -- Yes
> type ACL_TYPE_EXTENDED -- No
>=20
> If any of these results are unexpected, let me know, and I'll provide the
> configure tests.

The above looks right.  The second set of functions is only available
on FreeBSD and/or OS X, not in libacl, so that's fine.  Same goes for
ACL_TYPE_EXTENDED.

> I'll start working with the new build to see if anything unexpected happe=
ns.
> Is there anything in particular that I should check?

Does it fail to create ACLs?  Do the created ACLs make sense?  If you
have a file created with Cygwin >=3D 2.4.0 and change the file content
with Emacs, does the ACL change or stay the same?  Stuff like that.

No reason to check the Windows ACL with icacls btw., simple checks with
getfacl/setfacl will do.


Thanks a lot for testing!
Corinna

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

--da4uJneut+ArUgXk
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWpVboAAoJEPU2Bp2uRE+gWdAP/3bdEuWn6Tmu0u/7zVQuF4fV
tK1ty2BDUmMHVDtmtwhQfPU4Y9KTdeHnPMRGxMIdydMgFYvR1C9JFirzmb8a3/D5
xZaK54y5giSmmswogFZYgELVzVRhUwnNiiZWLFFXLDUVPmyzze0kPf8jz5UPFkdZ
Fpvpl5kk7mbt6VmcipmVuuE6tyWfrNHkx/fUbggCEcWTDpwZbXOcne0zHYqA01gj
kfO3kmC1Ndn5exhmYJUhnCmj0mO4D65QWJFHN9ufm/UCD3tsKomUazNd3xMdEVSi
ECRcURVP38nnsZW07HdF7evBCn52gWZCKQ4Fc16BOGJPQL+DrbpKeJ4ixclM2fKl
yjHOHcwBQJP0CwCJsQl+rn2GW2O5+9h6RgjdcRD47o838JmCOWC5wvOpmrWXPOkx
FRcFfI2Bxyuf1qeC1rvCXGLlTe5Kx8RSkUuM/TBeKYAVgCpXLx2RIVbw7D9yFrtE
llk2nrE5zfTXFGf47EuC0hUsBZsExp7oMjC+cZUkbqPm1e1rzdPgb9HT+bmCIJ83
ItGKPg/arlSbJaIpkRzOlmrUONvsmdtZBgeuYQxwnFT6O3fLNAQtumH9lO51UzLK
DtlXtakEtaQmk12V9eBUPLvlSWa1o3rBH0izAF3n0u0ebB5D0+YibDOqmoflFjjo
0XHk4xVxfqsgT2sS+HKr
=30Be
-----END PGP SIGNATURE-----

--da4uJneut+ArUgXk--

- Raw text -