DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 52VIoB2u1875968
Date: Mon, 31 Mar 2025 20:49:42 +0200
To: cygwin@cygwin.com
Subject: Re: acl man pages {and others?} (Was: symbolic link curiosity in
 3.6.0)
Message-ID: <Z-rjxlxWsCZ2T8HN@calimero.vinschen.de>
Mail-Followup-To: cygwin@cygwin.com
References: <Pine.BSF.4.63.2503250218240.74063@m0.truegem.net>
 <11037686.3WhfQktd6Z@nimes> <Z-fINO05FlFrTIUs@calimero.vinschen.de>
 <7892953.SKYDtnEIZr@nimes>
 <20b30d5f-2e2d-4abb-a391-5956d98345b8@SystematicSW.ab.ca>
 <jkbpzugorztmkphew4jwoybfwywje5e5xn6dfpbfk2lso6u45o@eezmf2m57vv2>
 <cwf5m5oemcbqxo2ppgfigglbnmp3dbu6tdkov66wsw45sijunf@l4boe6wekhs7>
 <a0dce911-e661-45d4-aa6f-d1cc7fb1deba@systematicsw.ab.ca>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <a0dce911-e661-45d4-aa6f-d1cc7fb1deba@systematicsw.ab.ca>
Precedence: list
From: Corinna Vinschen via Cygwin <cygwin@cygwin.com>
Reply-To: cygwin@cygwin.com
Cc: Corinna Vinschen <corinna-cygwin@cygwin.com>
Content-Type: text/plain; charset="utf-8"
Errors-To: cygwin-bounces~archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie.com@cygwin.com>
Content-Transfer-Encoding: 8bit

On Mar 31 12:35, Brian Inglis via Cygwin wrote:
> On 2025-03-29 13:08, Alejandro Colomar wrote:
> > On Sat, Mar 29, 2025 at 07:45:27PM +0100, Alejandro Colomar wrote:
> > > Hi Bruno,
> > 
> > Oops, s/Bruno/Brian/  :)
> > 
> > > 
> > > On Sat, Mar 29, 2025 at 12:28:52PM -0600, Brian Inglis wrote:
> > > > On 2025-03-29 05:43, Bruno Haible via Cygwin wrote:
> > > > > Regarding what acl_extended_file() does, there is the man page by
> > > > > Andreas Grünbacher:
> > > > > https://www.kernel.org/doc/man-pages/online/pages/man3/acl_extended_file.3.html
> > > > > Gnulib is not the only user of acl_extended_file(); therefore I would
> > > > > suggest that Cygwin should follow that man page — regardless of Gnulib.
> > > > 
> > > > Hi Alex,
> > > > 
> > > > I noticed that the online man-pages include the acl docs (above) but the
> > > > distributed man-pages do not!
> > > 
> > > These pages are distributed as part of the act package.  On Debian,
> > > the package that provides these manual pages is 'libacl1-dev'.
> > > 
> > > 	alx@devuan:~$ apt-file find acl_extended_file.3
> > > 	libacl1-dev: /usr/share/man/man3/acl_extended_file.3.gz
> > > 
> > > > Would you please consider including the acl project man pages?
> > > > 
> > > > 	https://git.savannah.nongnu.org/gitweb/?p=acl.git;a=tree;f=man
> > > 
> > > I think it's better to keep them within the acl project, unless they
> > > want us to take over.
> 
> I would consider packaging libacl unless it is Linux dependent if there is
> any Cygwin use case?

You can't do that.  Cygwin already provides most functions from libacl.
Cygwin even provides the acl/libacl.h header.

> Otherwise, I would consider creating a new man-pages-extra package,
> including libacl, and any other package man pages where the package is not
> part of Cygwin, but the API is?

Sounds like a nice idea.

> These man pages are available at man7.org as part of what Michael Kerrisk
> makes available online as part of Linux man pages:
> 
> 	https://man7.org/linux/man-pages/dir_by_project.html
> 
> Has anyone a feel if there are any other projects on that list whose man
> pages would be useful under Cygwin even if the package itself is not
> available, or even individual man pages where they are not currently
> available?

We have quite a few functions which might be only available on BSD systems,
and we have these Solaris ACL functions which don't exist on Linux.  We
probably can't use the man pages from Solaris due to copyright constraints,
but the FreeBSD man pages should be ok.  In terms of the POSIX.1e draft
17 ACL functions, the FreeBSD man pages (including acl.7) might be even
better suited than the libacl man pages, with just minor deletions of
non-existent functions.  And I'm going to add a few of the *_np functions
only available on FreeBSD/NetBSD anyway...


Corinna

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