Adding upstream version 4.22.0.upstream/4.22.0

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 165 insertions, 0 deletions

diff --git a/upstream/fedora-rawhide/man1/perlvos.1 b/upstream/fedora-rawhide/man1/perlvos.1
new file mode 100644
index 00000000..75ce383f
--- /dev/null
+++ b/upstream/fedora-rawhide/man1/perlvos.1
@@ -0,0 +1,165 @@
+.\" -*- mode: troff; coding: utf-8 -*-
+.\" Automatically generated by Pod::Man 5.01 (Pod::Simple 3.43)
+.\"
+.\" Standard preamble:
+.\" ========================================================================
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Vb \" Begin verbatim text
+.ft CW
+.nf
+.ne \\$1
+..
+.de Ve \" End verbatim text
+.ft R
+.fi
+..
+.\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>.
+.ie n \{\
+.    ds C` ""
+.    ds C' ""
+'br\}
+.el\{\
+.    ds C`
+.    ds C'
+'br\}
+.\"
+.\" Escape single quotes in literal strings from groff's Unicode transform.
+.ie \n(.g .ds Aq \(aq
+.el       .ds Aq '
+.\"
+.\" If the F register is >0, we'll generate index entries on stderr for
+.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
+.\" entries marked with X<> in POD.  Of course, you'll have to process the
+.\" output yourself in some meaningful fashion.
+.\"
+.\" Avoid warning from groff about undefined register 'F'.
+.de IX
+..
+.nr rF 0
+.if \n(.g .if rF .nr rF 1
+.if (\n(rF:(\n(.g==0)) \{\
+.    if \nF \{\
+.        de IX
+.        tm Index:\\$1\t\\n%\t"\\$2"
+..
+.        if !\nF==2 \{\
+.            nr % 0
+.            nr F 2
+.        \}
+.    \}
+.\}
+.rr rF
+.\" ========================================================================
+.\"
+.IX Title "PERLVOS 1"
+.TH PERLVOS 1 2024-01-25 "perl v5.38.2" "Perl Programmers Reference Guide"
+.\" For nroff, turn off justification.  Always turn off hyphenation; it makes
+.\" way too many mistakes in technical documents.
+.if n .ad l
+.nh
+.SH NAME
+perlvos \- Perl for Stratus OpenVOS
+.SH SYNOPSIS
+.IX Header "SYNOPSIS"
+This file contains notes for building perl on the Stratus OpenVOS
+operating system.  Perl is a scripting or macro language that is
+popular on many systems.  See perlbook for a number of good books
+on Perl.
+.PP
+These are instructions for building Perl from source.  This version of
+Perl requires the dynamic linking support that is found in OpenVOS
+Release 17.1 and thus is not supported on OpenVOS Release 17.0 or
+earlier releases.
+.PP
+If you are running VOS Release 14.4.1 or later, you can obtain a
+pre-compiled, supported copy of perl by purchasing the GNU Tools
+product from Stratus Technologies.
+.SH "BUILDING PERL FOR OPENVOS"
+.IX Header "BUILDING PERL FOR OPENVOS"
+To build perl from its source code on the Stratus V Series platform
+you must have OpenVOS Release 17.1.0 or later, GNU Tools Release
+3.5 or later, and the C/POSIX Runtime Libraries.
+.PP
+Follow the normal instructions for building perl; e.g, enter bash, run
+the Configure script, then use "gmake" to build perl.
+.SH "INSTALLING PERL IN OPENVOS"
+.IX Header "INSTALLING PERL IN OPENVOS"
+.IP 1. 4
+After you have built perl using the Configure script, ensure that you
+have modify and default write permission to \f(CW\*(C`>system>ported\*(C'\fR and
+all subdirectories.  Then type
+.Sp
+.Vb 1
+\&     gmake install
+.Ve
+.IP 2. 4
+While there are currently no architecture-specific extensions or
+modules distributed with perl, the following directories can be
+used to hold such files (replace the string VERSION by the
+appropriate version number):
+.Sp
+.Vb 1
+\&     >system>ported>lib>perl5>VERSION>i786
+.Ve
+.IP 3. 4
+Site-specific perl extensions and modules can be installed in one of
+two places.  Put architecture-independent files into:
+.Sp
+.Vb 1
+\&     >system>ported>lib>perl5>site_perl>VERSION
+.Ve
+.Sp
+Put site-specific architecture-dependent files into one of the
+following directories:
+.Sp
+.Vb 1
+\&     >system>ported>lib>perl5>site_perl>VERSION>i786
+.Ve
+.IP 4. 4
+You can examine the \f(CW@INC\fR variable from within a perl program
+to see the order in which Perl searches these directories.
+.SH "USING PERL IN OPENVOS"
+.IX Header "USING PERL IN OPENVOS"
+.SS "Restrictions of Perl on OpenVOS"
+.IX Subsection "Restrictions of Perl on OpenVOS"
+This port of Perl version 5 prefers Unix-style, slash-separated
+pathnames over OpenVOS-style greater-than-separated pathnames.
+OpenVOS-style pathnames should work in most contexts, but if you have
+trouble, replace all greater-than characters by slash characters.
+Because the slash character is used as a pathname delimiter, Perl
+cannot process OpenVOS pathnames containing a slash character in a
+directory or file name; these must be renamed.
+.PP
+This port of Perl also uses Unix-epoch date values internally.
+As long as you are dealing with ASCII character string
+representations of dates, this should not be an issue.  The
+supported epoch is January 1, 1980 to January 17, 2038.
+.PP
+See the file pod/perlport.pod for more information about the OpenVOS
+port of Perl.
+.SH "TEST STATUS"
+.IX Header "TEST STATUS"
+A number of the perl self-tests fails for various reasons; generally
+these are minor and due to subtle differences between common
+POSIX-based environments and the OpenVOS POSIX environment.  Ensure
+that you conduct sufficient testing of your code to guarantee that it
+works properly in the OpenVOS environment.
+.SH "SUPPORT STATUS"
+.IX Header "SUPPORT STATUS"
+I'm offering this port "as is".  You can ask me questions, but I
+can't guarantee I'll be able to answer them.  There are some
+excellent books available on the Perl language; consult a book
+seller.
+.PP
+If you want a supported version of perl for OpenVOS, purchase the
+OpenVOS GNU Tools product from Stratus Technologies, along with a
+support contract (or from anyone else who will sell you support).
+.SH AUTHOR
+.IX Header "AUTHOR"
+Paul Green (Paul.Green@stratus.com)
+.SH "LAST UPDATE"
+.IX Header "LAST UPDATE"
+February 28, 2013