rman: enable for all archs; trimmed down the patch file. (#10634)

- Removed all the "debian" subdir from the patches, as it is of no use on Haiku.
- Same with the patches for "contrib/*", as we're not packing any of it.
- Apply "contrib/gzip.patch" directly from the included sources.
- Kept Debian's fixes for the rman.1 man-page.
This commit is contained in:
OscarL
2024-06-26 04:51:54 -03:00
committed by GitHub
parent 4e36cb8f5b
commit debd1f29b0
3 changed files with 272 additions and 1524 deletions

File diff suppressed because it is too large Load Diff

View File

@@ -0,0 +1,266 @@
From e830381404a732540c3b177af31d9c796fbb4315 Mon Sep 17 00:00:00 2001
From: Oscar Lesta <oscar.lesta@gmail.com>
Date: Tue, 25 Jun 2024 23:48:51 -0300
Subject: Debian's fixes to rman.1
diff --git a/rman.1 b/rman.1
index 91e4c1e..2a592da 100644
--- a/rman.1
+++ b/rman.1
@@ -12,9 +12,9 @@ http://polyglotman.sourceforge.net/rman.html
\fIPolyglotMan \fR takes man pages from most of the popular flavors
of UNIX and transforms them into any of a number of text source
formats. PolyglotMan was formerly known as RosettaMan. The name
-of the binary is still called \fIrman \fR, for scripts that depend
+of the binary is still called \fIrman\fR, for scripts that depend
on that name; mnemonically, just think "reverse man". Previously \fI
-PolyglotMan \fR required pages to be formatted by nroff prior
+PolyglotMan \fR required pages to be formatted by nroff(1) prior
to its processing. With version 3.0, it \fIprefers [tn]roff source \fR
and usually produces results that are better yet. And source
processing is the only way to translate tables. Source format
@@ -24,7 +24,7 @@ translation as a backup.
In parsing [tn]roff source, one could implement an arbitrarily
large subset of [tn]roff, which I did not and will not do, so
the results can be off. I did implement a significant subset
-of those use in man pages, however, including tbl (but not eqn),
+of those used in man pages, however, including tbl (but not eqn),
if tests, and general macro definitions, so usually the results
look great. If they don't, format the page with nroff before
sending it to PolyglotMan. If PolyglotMan doesn't recognize a
@@ -34,7 +34,7 @@ what I can do. When running PolyglotMan with man page source
that includes or redirects to other [tn]roff source using the .so (source
or inclusion) macro, you should be in the parent directory of
the page, since pages are written with this assumption. For example,
-if you are translating /usr/man/man1/ls.1, first cd into /usr/man.
+if you are translating /usr/share/man/man1/ls.1, first cd into /usr/share/man.
.PP
\fIPolyglotMan \fR accepts man pages from: SunOS, Sun Solaris,
Hewlett-Packard HP-UX, AT&T System V, OSF/1 aka Digital UNIX,
@@ -52,70 +52,70 @@ http://polyglotman.sourceforge.net/ \fR.
The following options should not be used with any others and
exit PolyglotMan without processing any input.
.TP 15
--h|--help
+\-h|\-\-help
Show list of command line options and exit.
.TP 15
--v|--version
+\-v|\-\-version
Show version number and exit.
.PP
\fIYou should specify the filter first, as this sets a number
of parameters, and then specify other options.
.TP 15
--f|--filter <ASCII|roff|TkMan|Tk|Sections|HTML|SGML|MIME|LaTeX|LaTeX2e|RTF|POD>
+\-f|\-\-filter <ASCII|roff|TkMan|Tk|Sections|HTML|SGML|MIME|LaTeX|LaTeX2e|RTF|POD>
Set the output filter. Defaults to ASCII.
.TP 15
--S|--source
+\-S|\-\-source
PolyglotMan tries to automatically determine whether its input
is source or formatted; use this option to declare source input.
.TP 15
--F|--format|--formatted
+\-F|\-\-format|\-\-formatted
PolyglotMan tries to automatically determine whether its input
is source or formatted; use this option to declare formatted
input.
.TP 15
--l|--title \fIprintf-string \fR
+\-l|\-\-title \fIprintf-string \fR
In HTML mode this sets the <TITLE> of the man pages, given the
same parameters as \fI-r \fR.
.TP 15
--r|--reference|--manref \fIprintf-string \fR
+\-r|\-\-reference|\-\-manref \fIprintf-string \fR
In HTML and SGML modes this sets the URL form by which to retrieve
other man pages. The string can use two supplied parameters:
the man page name and its section. (See the Examples section.)
-If the string is null (as if set from a shell by "-r ''"), `-'
+If the string is null (as if set from a shell by "\-r ''"), `-'
or `off', then man page references will not be HREFs, just set
in italics. If your printf supports XPG3 positions specifier,
this can be quite flexible.
.TP 15
--V|--volumes \fI<colon-separated list> \fR
+\-V|\-\-volumes \fI<colon-separated list> \fR
Set the list of valid volumes to check against when looking for
cross-references to other man pages. Defaults to \fI1:2:3:4:5:6:7:8:9:o:l:n:p \fR(volume
names can be multicharacter). If an non-whitespace string in
the page is immediately followed by a left parenthesis, then
one of the valid volumes, and ends with optional other characters
and then a right parenthesis--then that string is reported as
-a reference to another manual page. If this -V string starts
+a reference to another manual page. If this \-V string starts
with an equals sign, then no optional characters are allowed
between the match to the list of valids and the right parenthesis. (This
option is needed for SCO UNIX.)
.PP
The following options apply only when formatted pages are given
-as input. They do not apply or are always handled correctly with
+as input. They do not apply to or are always handled correctly with
the source.
.TP 15
--b|--subsections
+\-b|\-\-subsections
Try to recognize subsection titles in addition to section titles.
This can cause problems on some UNIX flavors.
.TP 15
--K|--nobreak
+\-K|\-\-nobreak
Indicate manual pages don't have page breaks, so don't look for
-footers and headers around them. (Older nroff -man macros always
+footers and headers around them. (Older nroff \-man macros always
put in page breaks, but lately some vendors have realized that
-printout are made through troff, whereas nroff -man is used to
+printouts are made through troff(1), whereas nroff \-man is used to
format pages for reading on screen, and so have eliminated page
breaks.) \fIPolyglotMan \fR usually gets this right even without
this flag.
.TP 15
--k|--keep
+\-k|\-\-keep
Keep headers and footers, as a canonical report at the end of
the page. changeleft
Move changebars, such as those found in the Tcl/Tk manual pages,
@@ -124,24 +124,24 @@ to the left. --> notaggressive
which is on by default, page parsing elides headers and footers,
identifies sections and more. -->
.TP 15
--n|--name \fIname \fR
+\-n|\-\-name \fIname \fR
Set name of man page (used in roff format). If the filename is
given in the form " \fIname \fR. \fIsection \fR", the name and
section are automatically determined. If the page is being parsed
from [tn]roff source and it has a .TH line, this information
is extracted from that line.
.TP 15
--p|--paragraph
+\-p|\-\-paragraph
paragraph mode toggle. The filter determines whether lines should
be linebroken as they were by nroff, or whether lines should
be flowed together into paragraphs. Mainly for internal use.
.TP 15
--s|section \fI# \fR
+\-s|section \fI# \fR
Set volume (aka section) number of man page (used in roff format).
tables
Turn on aggressive table parsing. -->
.TP 15
--t|--tabstops \fI# \fR
+\-t|\-\-tabstops \fI# \fR
For those macros sets that use tabs in place of spaces where
possible in order to reduce the number of characters used, set
tabstops every \fI# \fR columns. Defaults to 8.
@@ -149,12 +149,12 @@ tabstops every \fI# \fR columns. Defaults to 8.
.SS "ROFF "
Some flavors of UNIX ship man page without [tn]roff source, making
one's laser printer little more than a laser-powered daisy wheel.
-This filer tries to intuit the original [tn]roff directives,
+This filter tries to intuit the original [tn]roff directives,
which can then be recompiled by [tn]roff.
.SS "TkMan "
-TkMan, a hypertext man page browser, uses \fIPolyglotMan \fR
+TkMan(1), a hypertext man page browser, uses \fIPolyglotMan \fR
to show man pages without the (usually) useless headers and footers
-on each pages. It also collects section and (optionally) subsection
+on each page. It also collects section and (optionally) subsection
heads for direct access from a pulldown menu. TkMan and Tcl/Tk,
the toolkit in which it's written, are available via anonymous
ftp from \fIftp://ftp.smli.com/pub/tcl/ \fR
@@ -164,27 +164,27 @@ of text-tags pairs, where tag names roughly correspond to HTML.
This output can be inserted into a Tk text widget by doing an \fI
eval <textwidget> insert end <text> \fR. This format should be
relatively easily parsible by other programs that want both the
-text and the tags. Also see ASCII.
+text and the tags. See also ASCII.
.SS "ASCII "
When printed on a line printer, man pages try to produce special
text effects by overstriking characters with themselves (to produce
bold) and underscores (underlining). Other text processing software,
such as text editors, searchers, and indexers, must counteract
this. The ASCII filter strips away this formatting. Piping nroff
-output through \fIcol -b \fR also strips away this formatting,
+output through \fIcol \-b \fR also strips away this formatting,
but it leaves behind unsightly page headers and footers. Also
see Tk.
.SS "Sections "
Dumps section and (optionally) subsection titles. This might
be useful for another program that processes man pages.
.SS "HTML "
-With a simple extention to an HTTP server for Mosaic or other
+With a simple extention to a HTTP server for Mosaic(1) or other
World Wide Web browser, \fIPolyglotMan \fR can produce high quality
HTML on the fly. Several such extensions and pointers to several
others are included in \fIPolyglotMan \fR's \fIcontrib \fR directory.
.SS "SGML "
This is appoaching the Docbook DTD, but I'm hoping that someone
-that someone with a real interest in this will polish the tags
+with a real interest in this will polish the tags
generated. Try it to see how close the tags are now.
.SS "MIME "
MIME (Multipurpose Internet Mail Extensions) as defined by RFC 1563,
@@ -194,8 +194,8 @@ enriched documents.
Why not?
.SS "RTF "
Use output on Mac or NeXT or whatever. Maybe take random man
-pages and integrate with NeXT's documentation system better.
-Maybe NeXT has own man page macros that do this.
+pages and integrate them better with NeXT's documentation system.
+Maybe NeXT has its own man page macros that do this.
.SS "PostScript and FrameMaker "
To produce PostScript, use \fIgroff \fR or \fIpsroff \fR. To
produce FrameMaker MIF, use FrameMaker's builtin filter. In both
@@ -206,7 +206,7 @@ roff filter first.
To convert the \fIformatted \fR man page named \fIls.1 \fR back
into [tn]roff source form:
.PP
-\fIrman -f roff /usr/local/man/cat1/ls.1 > /usr/local/man/man1/ls.1 \fR
+\fIrman \-f roff /usr/local/man/cat1/ls.1 > /usr/local/man/man1/ls.1 \fR
.br
.PP
Long man pages are often compressed to conserve space (compression
@@ -217,27 +217,27 @@ don't distinguish subsections well enough for \fIPolyglotMan \fR
to detect them). Let's convert this to LaTeX format:
.br
.PP
-\fIpcat /usr/catman/a_man/cat1/automount.z | rman -b -n automount -s 1 -f
+\fIpcat /usr/catman/a_man/cat1/automount.z | rman \-b \-n automount \-s 1 \-f
latex > automount.man \fR
.br
.PP
-Alternatively, \fIman 1 automount | rman -b -n automount -s 1 -f
+Alternatively, \fIman 1 automount | rman \-b \-n automount \-s 1 \-f
latex > automount.man \fR
.br
.PP
For HTML/Mosaic users, \fIPolyglotMan \fR can, without modification
of the source code, produce HTML links that point to other HTML
man pages either pregenerated or generated on the fly. First
-let's assume pregenerated HTML versions of man pages stored in \fI/usr/man/html \fR.
+let's assume pregenerated HTML versions of man pages stored in \fI/usr/share/man/html \fR.
Generate these one-by-one with the following form:
.br
-\fIrman -f html -r 'http:/usr/man/html/%s.%s.html' /usr/man/cat1/ls.1 > /usr/man/html/ls.1.html \fR
+\fIrman \-f html \-r 'http:/usr/share/man/html/%s.%s.html' /usr/share/man/cat1/ls.1 > /usr/share/man/html/ls.1.html \fR
.br
.PP
If you've extended your HTML client to generate HTML on the fly
you should use something like:
.br
-\fIrman -f html -r 'http:~/bin/man2html?%s:%s' /usr/man/cat1/ls.1 \fR
+\fIrman \-f html \-r 'http:~/bin/man2html?%s:%s' /usr/share/man/cat1/ls.1 \fR
.br
when generating HTML.
.SH "BUGS/INCOMPATIBILITIES "
@@ -248,7 +248,7 @@ man pages to light editing.
Tables in formatted pages, especially H-P's, aren't handled very
well. Be sure to pass in source for the page to recognize tables.
.PP
-The man pager \fIwoman \fR applies its own idea of formatting
+The man pager \fIwoman\fR(1) applies its own idea of formatting
for man pages, which can confuse \fIPolyglotMan \fR. Bypass \fI
woman \fR by passing the formatted manual page text directly
into \fIPolyglotMan \fR.

View File

@@ -1,16 +1,15 @@
SUMMARY="Man page viewer and translator"
DESCRIPTION="
Parse formatted man pages and man page source from most flavors of UNIX. \
DESCRIPTION="Parse formatted man pages and man page source from most flavors of UNIX. \
Convert to HTML, ASCII, TkMan, DocBook, and other formats."
HOMEPAGE="https://sourceforge.net/projects/polyglotman/"
COPYRIGHT="2003 Thomas A. Phelps"
LICENSE="Artistic"
REVISION="3"
REVISION="4"
SOURCE_URI="http://downloads.sourceforge.net/project/polyglotman/polyglotman/3.2/rman-3.2.tar.gz"
CHECKSUM_SHA256="68a130696b251966db10a4774e2bc8083a0147b83f64c11e9bb4cd654da32d5f"
PATCHES="rman-3.2.patch"
PATCHES="rman-3.2.patchset"
ARCHITECTURES="x86_gcc2 ?x86"
ARCHITECTURES="all"
PROVIDES="
rman = $portVersion
@@ -27,10 +26,12 @@ BUILD_PREREQUIRES="
cmd:gcc
cmd:ld
cmd:make
cmd:patch
"
BUILD()
{
patch rman.c < contrib/gzip.patch
make BINDIR=$binDir MANDIR=$manDir
}