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
Unknown Object (File)
Mon, Jul 7, 2:29 PM
Unknown Object (File)
Fri, Jul 4, 2:31 PM
Unknown Object (File)
Mon, Jun 30, 9:04 AM
Unknown Object (File)
Thu, Jun 26, 1:33 PM
Unknown Object (File)
Wed, Jun 25, 2:43 AM
Unknown Object (File)
Fri, Jun 20, 6:37 AM
Unknown Object (File)
May 17 2025, 2:08 PM
Unknown Object (File)
Mar 16 2025, 4:14 PM

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