Date: Mon, 04 Sep 2023 17:44:51 +0000 From: bugzilla-noreply@freebsd.org To: doc@FreeBSD.org Subject: [Bug 273245] textproc/groff: groff_mdoc(7): output from 'man 7 groff_mdoc' is badly broken Message-ID: <bug-273245-9-hyZaRNMPp4@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-273245-9@https.bugs.freebsd.org/bugzilla/> References: <bug-273245-9@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D273245 Wolfram Schneider <wosch@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Affects Some People |Affects Many People CC| |yasu@freebsd.org Status|New |Open --- Comment #4 from Wolfram Schneider <wosch@FreeBSD.org> --- (In reply to G. Branden Robinson from comment #3) Are you aware that this tiny change (-man -> -mandoc) will break some of our core FreeBSD tools, and a lot of third-party tools which we use in the base system? Not to mention some FreeBSD ports which may fail as well. This will affect all FreeBSD releases/branches (12/13/14/15) that we suppor= t. A possible workaround is to downgrade the groff port to 1.22.4 locally. Checking our repos I see that we need to change ~100 files: for i in freebsd-{src,ports,doc};do (cd $i && printf "$i "; git grep 'roff.* -man[^d]' |wc -l );done freebsd-src 35 freebsd-ports 51 freebsd-doc 9 Thinking about the issue - maybe we should just patch the FreeBSD port of g= roff and revert this change. It hurts a lot of our users. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-273245-9-hyZaRNMPp4>