On 2025-03-31 12:49, Corinna Vinschen via Cygwin wrote:
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.

Figures!

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.

The Solaris man pages were made available under the CDDL or PDL derived from MPL: we have Solaris 10 and OpenSolaris 2010 available on the freebsd.org site, a well as most other OSes anyone might want: 520 of them, from 7th Edition, 2.10BSD, 386BSD, thru 4.4Lite2, .

Space required for FreeBSD man pages is comparable to man-pages-linux - should we make all FreeBSD 15.0 current man pages available similar to man-pages-linux - man-pages-freebsd package and directory under /usr/share/man/ symlinked as freebsd for convenience with man -m|--systems SYSTEM,...?

Or should we stick to the original idea and package only selected missing man pages in the other sections of posix.xml as man-pages-extra?

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...




--
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retrancher  but when there is no more to cut
                                -- Antoine de Saint-Exupéry

--
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

Reply via email to