History log of /openbsd-src/gnu/usr.bin/perl/cpan/Pod-Perldoc/lib/Pod/Perldoc/ToMan.pm (Results 1 – 24 of 24)
Revision Date Author Comments
# e0a54000 28-Jan-2025 afresh1 <afresh1@openbsd.org>

Apply local patches - perl-5.40.1

ok sthen@
sooner rather than later deraadt@


# 3d61058a 28-Jan-2025 afresh1 <afresh1@openbsd.org>

Fix merge issues, remove excess files - match perl-5.40.1 dist

ok sthen@
sooner rather than later deraadt@


# fac98b93 14-May-2024 afresh1 <afresh1@openbsd.org>

Apply local patches - perl-5.38.2

ok gkoehler@
Commit and we'll fix fallout bluhm@
Right away, please deraadt@


# e0680481 14-May-2024 afresh1 <afresh1@openbsd.org>

Fix merge issues, remove excess files - match perl-5.38.2 dist

ok gkoehler@
Commit and we'll fix fallout bluhm@
Right away, please deraadt@


# fdcd7346 15-Feb-2023 afresh1 <afresh1@openbsd.org>

Apply local patches - perl-5.36.0

OK bluhm@
a good time naddy@


# eac174f2 15-Feb-2023 afresh1 <afresh1@openbsd.org>

Fix merge issues, remove excess files - match perl-5.36.0 dist

OK bluhm@
a good time naddy@


# 9dc91179 01-Mar-2021 afresh1 <afresh1@openbsd.org>

Apply local patches, remove excess files - perl-5.32.1

OK sthen@


# 56d68f1e 01-Mar-2021 afresh1 <afresh1@openbsd.org>

Fix merge issues, remove excess files - match perl-5.32.1 dist

OK sthen@


# d0bd1485 30-Dec-2019 afresh1 <afresh1@openbsd.org>

Apply local patches, remove excess files - perl-5.30.1

Timing is good deraadt@, OK sthen@


# b46d8ef2 30-Dec-2019 afresh1 <afresh1@openbsd.org>

Fix merge issues, remove excess files - match perl-5.30.1 dist

Timing is good deraadt@, OK sthen@


# 81203fd3 14-Jun-2019 schwarze <schwarze@openbsd.org>

Delete totally bogus code specifically targetted at mandoc
which tried to figure out whether mandoc supported UTF-8 output
(which it has been doing since 2011) and which passed the -T locale
option (

Delete totally bogus code specifically targetted at mandoc
which tried to figure out whether mandoc supported UTF-8 output
(which it has been doing since 2011) and which passed the -T locale
option (which has been the default since 2014 and always will)
but which required the -V option to work (which was deleted half
a decade ago and will not come back).
Nowadays, it is safe to assume that mandoc just works with UTF-8
on both the input and output sides - in literally each and every
operating system providing a mandoc port or package, even those
that are seriously lagging behind.
This patch will also be pushed upstream.
OK tb@

show more ...


# 6396a31b 06-Jun-2019 afresh1 <afresh1@openbsd.org>

Reapply patches lost in the perl 5.28.2 update


# e603c72f 24-May-2019 afresh1 <afresh1@openbsd.org>

Update to perl 5.28.2

Minor bugfixes and documentation improvments. See perldelta for details.
https://metacpan.org/pod/release/SHAY/perl-5.28.2/pod/perldelta.pod

OK bluhm@


# 73264f3b 05-May-2019 schwarze <schwarze@openbsd.org>

The perldoc(1) program wants to support the MANWIDTH environment
variable and fall back to what stty(1) reports, and it does so with
nroff(1), but it didn't with mandoc(1) because it didn't know how

The perldoc(1) program wants to support the MANWIDTH environment
variable and fall back to what stty(1) reports, and it does so with
nroff(1), but it didn't with mandoc(1) because it didn't know how
to pass the desired width to mandoc. Teach it to use "-O width=".
OK afresh1@.

I noticed the unimplemented feature when Andrew Daugherity asked
on tech@ what the point of a certain patch in FreeBSD is (which it
turns out we don't need).

show more ...


# e1ef61ef 05-May-2019 schwarze <schwarze@openbsd.org>

Like we already do for pod2man(1), always let perldoc(1) produce man(7)
output in UTF-8 encoding on OpenBSD. The consumer is always mandoc(1)
on OpenBSD, which can always handle UTF-8 input (no matt

Like we already do for pod2man(1), always let perldoc(1) produce man(7)
output in UTF-8 encoding on OpenBSD. The consumer is always mandoc(1)
on OpenBSD, which can always handle UTF-8 input (no matter what LC_CTYPE
is) and which always produces useful output: UTF-8 for LC_CTYPE=*.UTF-8
or ASCII otherwise, in particular for LC_CTYPE=C.

Patch written after afresh1@ reported that "perldoc -oman" output
looked bad in both output modes.
OK afresh1@.

show more ...


# 4b70baf6 04-May-2019 afresh1 <afresh1@openbsd.org>

Fix Pod::Perldoc::ToMan and use it as the default perldoc formatter

From Andrew Daugherity <andrew.daugherity () gmail ! com>

Corrections to fix and OK millert@, suggestions and OK schwarze@


# 9f11ffb7 13-Feb-2019 afresh1 <afresh1@openbsd.org>

Fix merge issues, remove excess files - match perl-5.28.1 dist

looking good sthen@, Great! bluhm@


# b8851fcc 05-Feb-2017 afresh1 <afresh1@openbsd.org>

Fix merge issues, remove excess files - match perl-5.24.1 dist


# 0b7734b3 25-Jul-2016 afresh1 <afresh1@openbsd.org>

Patch perl CVE-2016-1238

The problem relates to Perl 5 ("perl") loading modules from the
includes directory array ("@INC") in which the last element is the
current directory ("."). That means that,

Patch perl CVE-2016-1238

The problem relates to Perl 5 ("perl") loading modules from the
includes directory array ("@INC") in which the last element is the
current directory ("."). That means that, when "perl" wants to
load a module (during first compilation or during lazy loading of
a module in run-time), perl will look for the module in the current
directory at the end, since '.' is the last include directory in
its array of include directories to seek. The issue is with requiring
libraries that are in "." but are not otherwise installed.

The major problem with this behavior is that it unexpectedly puts
a user at risk whenever they execute any Perl scripts from a directory
that is writable by other accounts on the system. For instance, if
a user is logged in as root and changes directory into /tmp or an
account's home directory, it is possible to now run any shell
commands that are written in C, Python or Ruby without fear.

The same isn't true for any shell commands that are written in Perl,
since a significant proportion of Perl scripts will execute code
in the current working directory whenever they are run. For example,
if a user on a shared system creates the file /tmp/Pod/Perldoc/Toterm.pm,
and then I log in as root, change directory to /tmp, and run "perldoc
perlrun", it will execute the code they have placed in the file.


ok deraadt@

show more ...


# e5157e49 17-Nov-2014 afresh1 <afresh1@openbsd.org>

Fix merge conflicts, remove extra files, match upstream perl-5.20.1

ok deraadt@ sthen@ espie@ miod@


# e9ce3842 24-Mar-2014 afresh1 <afresh1@openbsd.org>

Merge perl-5.18.2 plus local patches, remove old files

OK espie@ sthen@ deraadt@


# af9ddab1 04-Jun-2013 schwarze <schwarze@openbsd.org>

Do not feed UTF-8 input into mandoc or nroff
because that resulted in corrupt output.

This is a verbatim backport of the following bugfix from upstream git master:
https://rt.cpan.org/Public/Bug/Dis

Do not feed UTF-8 input into mandoc or nroff
because that resulted in corrupt output.

This is a verbatim backport of the following bugfix from upstream git master:
https://rt.cpan.org/Public/Bug/Display.html?id=77465
https://github.com/mrallen1/Pod-Perldoc/commit/6e1541d0bcb74a7b2b9ee3235d57953fb800bb67

Do not take the comment in the source code too literally.
It doesn't really explain the problem well.

OK sthen@ espie@ millert@

show more ...


# aa5e9e10 03-Jun-2013 schwarze <schwarze@openbsd.org>

Only produce UTF-8 output if the user's locale asks for it.
Will send this upstream as well.
OK millert@ bluhm@ stsp@


# 898184e3 25-Mar-2013 sthen <sthen@openbsd.org>

import perl 5.16.3 from CPAN - worked on by Andrew Fresh and myself