Page MenuHomeFreeBSD

Create EX_*.3 manual page links to sysexits.3
AbandonedPublic

Authored by 0mp on Mar 30 2020, 5:08 PM.
Tags
None
Referenced Files
F80164493: D24224.id70006.diff
Thu, Mar 28, 6:58 PM
Unknown Object (File)
Feb 20 2024, 9:20 AM
Unknown Object (File)
Jan 16 2024, 7:13 PM
Unknown Object (File)
Dec 13 2023, 3:47 AM
Unknown Object (File)
Dec 7 2023, 9:09 PM
Unknown Object (File)
Nov 27 2023, 9:25 AM
Unknown Object (File)
Nov 15 2023, 4:15 AM
Unknown Object (File)
Oct 12 2023, 6:08 AM

Details

Reviewers
bcr
ngie
emaste
Summary
Create EX_*.3 manual page links to sysexits.3
Test Plan
export DESTDIR=/tmp/test1234
mkdir -p $DESTDIR

make hierarchy DESTDIR=$DESTDIR
cd share/man/man3
make build
make install DESTDIR=$DESTDIR

# Check /tmp/test1234

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 30187
Build 27980: arc lint + arc unit

Event Timeline

I'm looking for a review of 1 thing, really: is it beneficial to actually create those MLINKS.

After a quick chat with some other developers it looks like we would actually want to deprecate sysexits.

In D24224#533296, @0mp wrote:

After a quick chat with some other developers it looks like we would actually want to deprecate sysexits.

Thank you very much for taking the charge in cleaning up manpages, etc!

FWIW, I don't think it would be a good idea to document individual error codes. We don't have manpage links for EINVAL.2, etc, to errno(2).

As long as we're consistent with POSIX's documentation, I believe we're ok with the status quo, which is leaving the individual error codes documented only in sysexits(3).