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=vUKNaW1tZxpEAiGZNzT/CHOvmar0b+NBPN2/U599+LWYTMhlC7Ewy
	BnnjoaD1HQkyZw+cvem75w7aFrIBcmmImZady81n32Ls2hZBqxcCYgts/gMV0pK9
	ISUp5WEatrnSMk5RJqtUocGqBHPTpNQYOUeqRsukqFja9kjpDmhuPQ=
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=p3xlWuY9Ol60uBNZaNLVtvXCkrQ=; b=NpkoxMRaarPrwfAl/Bv3TXx1F/SU
	oo8hstDF4shii50mPRwXBgAwndIcYqHwUyik1ZDvuZEtYB1mnH0MeYQTWnIj61o+
	MsBRdYNfaG1wyncg6UhasEBTpL8/QXGBEirrPHH8ZqFhfe+KJHCcD2Q0w4NxA/3p
	R/GEZmnXZb9jUGc=
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:	=?ISO-8859-1?Q?No, score=-101.4 required=5.0 tests=BAYES_00,GOOD_FROM_CORINNA_CYGWIN,KAM_LAZY_DOMAIN_SECURITY,KB_WAM_FROM_NAME_SINGLEWORD,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:1489, BSD=e2, bsd=e2, OS=e2?=
X-HELO:	drew.franken.de
Date:	Wed, 15 Nov 2017 08:59:26 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: BSD file flags support in Cygwin?
Message-ID:	<20171115075926.GL6054@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<D62F6895.F75A%billziss AT navimatics DOT com> <20171114100658 DOT GH6054 AT calimero DOT vinschen DOT de> <D6307C50.F768%billziss AT navimatics DOT com>
MIME-Version:	1.0
In-Reply-To:	<D6307C50.F768%billziss@navimatics.com>
User-Agent:	Mutt/1.9.1 (2017-09-22)

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

On Nov 14 19:17, Bill Zissimopoulos wrote:
> Corinna, thanks for your answer.
>=20
> My question was largely to confirm my understanding as I probably do not
> have time to produce such a patch currently. For the benefit of the
> discussion and to assist any future attempts at doing this:
>=20
> Chflags(2) and friends would be relatively easy to implement. OTOH the
> BSD=E2=80=99s and OSX use stat(2) to report file flags in st_flags. Since=
 Cygwin
> lacks an st_flags field, we would have to somehow change struct stat to
> accommodate it. Do you have guidance on how to handle such a change? Would
> you even want such a change? [I suspect not.]

You're right.  Struct stat is exposed to user space so changing this is
bound to break existing applications.  We *might* get away lightly with
just adding a member to the end as in this case, but is the support for
DOS flags actually worth it?  It's still a hassle to support new and old
apps in Cygwin in such cases.

> [I know some OS=E2=80=99es have had to deal with stat(2) changes over the=
 years,
> but I am not as familiar with Cygwin history.]

An executable has the version info of the Cygwin version at the
time of building compiled in.  This is used in Cygwin to check
what an executable expects.

See winsup/cygwin/include/cygwin/version.h and the usage of the
checks throughout the code.


Corinna

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

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

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

iQIcBAEBCAAGBQJaC/PeAAoJEPU2Bp2uRE+g4vYQAJ1xiBjJTv1dOakhzLzUhxsY
h/0erGoFA7MNcjm6b7YY5fRYdQrAJ7/qhUzBRM+Kx5Z4uCsgmiWnzxtXVJopQFmE
lfwKgIUo+28+cWTYS0h1QvaLfzNACrSWGiTaDQxaB8jGf3fupld52sUlca/gAWMY
2zv85TqkADvF01gEdfp046uGcZud8jPjSGvY0t56xkTNWyVTqsnjCbwGEeJ8G7Fi
DLzAuE7BmArE/kcFSrsJixBbq/yYr2d0D5VkMcEg3Vymdte2+//idkbZOWKtRxjg
6iJwjN2P6LOm1z6X9YT7yDwLzkzRfgGuFHOWVeExOhVsr0F9gnN1hj8DIsjpQ4ki
NH/xCt0XwpL+BD8kpfO/gNRx46bTc0c4SGZ4yoO5/S0ppzJdZ/9ak8SZcKzwFxrr
IjbPDufTL6SHCamV3Xi0Xp910ge/ELty8EpvbXSRvKLVinbaXfRDqxzQqTIAiaMC
Hyf8qyhKrRk5xWoYozl8TbdZ3jWvXTc6qV751wZGle0t+cxBql5TfEx2j0bL7hl8
n+XIIW4jF3KqzLmr5vnIx+tlvgO5B3XUcgM6/ELOqeotAlh9GN37YnPbjT9Ytw6X
QhFqj/HeOFZmecmlvay3Qq1Wdx8qXnWIa2sxTeFYUxanguqF8riCvIIil3TnjNVW
CPY0xH5U28BbDKVTLx6W
=hzuc
-----END PGP SIGNATURE-----

--NGIwU0kFl1Z1A3An--

- Raw text -