Web lists-archives.com

Re: BSD file flags support in Cygwin?




Corinna, thanks for your answer.

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:

Chflags(2) and friends would be relatively easy to implement. OTOH the
BSD’s 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.]

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

Bill



On 11/14/17, 2:06 AM, Corinna Vinschen wrote:

>On Nov 13 23:21, Bill Zissimopoulos wrote:
>> Does Cygwin have any support for BSD file flags (UF_* flags, such as
>> UF_HIDDEN, etc.)? These flags are often used to provide support for
>> Windows file attributes (FILE_ATTRIBUTE_*, such as
>>FILE_ATTRIBUTE_HIDDEN).
>> 
>> OSX and FreeBSD provide such support during stat(2) and chflags(2). I
>> expect that Cygwin does not have such support, but wanted to
>>double-check.
>> 
>> 
>>https://www.freebsd.org/cgi/man.cgi?query=chflags&apropos=0&sektion=2&man
>>pa
>> th=FreeBSD+11.1-RELEASE+and+Ports&arch=default&format=html
>
>No, we don't support this.  We couldn't support it via stat anyway,
>only via the extra chflags function group.  Patches welcome, as
>long as it's the entire group of functions so chflags(1) compiles
>OOTB.
>
>
>Corinna
>
>-- 
>Corinna Vinschen                  Please, send mails regarding Cygwin to
>Cygwin Maintainer                 cygwin AT cygwin DOT com
>Red Hat


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple