From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.5.0-0.1
Date: Sun, 24 Jan 2016 19:30:00 -0000 [thread overview]
Message-ID: <announce.20160124115654.GB11514@calimero.vinschen.de> (raw)
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.
Since the year 2000, Cygwin supports a POSIXoid ACL emulation. This
emulation is based on the Solaris API, which is only marginally
comparable to the POSIX ACL API defined in the withdrawn draft
POSIX.1e(*).
At about the same time SGI started to implement POSIX.1e which
eventually became libacl in 2001. Libacl is the POSIX ACL
implementation used on Linux.
With Cygwin 2.4.0, Cygwin introduced a major revamp of the POSIX ACL
emulation. This new emulation is complete in the sense that the ACL
handling covers all of POSIX.1e quirks. This in turn allows to use
the POSIX.1e API.
The Solaris API is the base implementation and stays available. The
POSIX.1e API is implemented in terms of the Solaris types and mainly
a slim layer on top of the Solaris API.
Changes for developers:
- The full set of POSIX.1e functions is now available.
- Most of the libacl extensions are available as well. The only
exceptions right now are the two functions perm_copy_file and
perm_copy_fd. These can be added later. Somebody just has to do it :)
- The <sys/acl.h> header now *only* exposes the POSIX.1e API.
- To get access to the Solaris API, you will have to include
<cygwin/acl.h> now.
- There's a new header <acl/libacl.h> which exposes the libacl extension
functions.
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...
Have fun,
Corinna
(*) http://wt.tuxomania.net/publications/posix.1e/
--
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
next reply other threads:[~2016-01-24 11:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-24 19:30 Corinna Vinschen [this message]
2016-01-24 22:32 ` Ken Brown
2016-01-25 2:55 ` Corinna Vinschen
2016-01-25 9:29 ` Ken Brown
2016-01-25 14:58 ` Corinna Vinschen
2016-01-25 9:30 ` Thorsten Kampe
2016-01-25 11:02 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=announce.20160124115654.GB11514@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).