代码拉取完成,页面将自动刷新
同步操作将从 openKylin/perl 强制同步,此操作会覆盖自 Fork 仓库以来所做的任何修改,且无法恢复!!!
确定后同步将在后台操作,完成时将刷新页面,请耐心等待。
If you read this file _as_is_, just ignore the funny characters you
see. It is written in the POD format (see pod/perlpod.pod) which is
specifically designed to be readable as is.
=head1 NAME
PACKAGING - notes and best practice for packaging perl 5
=head1 SYNOPSIS
This document is aimed at anyone who is producing their own version of
perl for distribution to other users. It is intended as a collection
of useful tips, advice and best practice, rather than being a complete
packaging manual. The starting point for installing perl remains
F<INSTALL>.
=head1 Customizing test running
A small number of porting tests (those in t/porting) are not well suited
to typical distribution packaging scenarios. For example, they assume
they are working in a git clone of the upstream Perl repository, or
enforce rules which are not relevant to downstream packagers. These can
be skipped by setting the environment variable PERL_BUILD_PACKAGING.
A complete list of tests which this applied to can be found by searching
the codebase for this string.
An alternative strategy would be to skip all porting tests, but many of
them are useful if additional patches might be applied.
=head1 Customizing patchlevel to advertise your local patches
You can advertise your custom local patches by using patchlevel.h as a
standalone Perl script.
=head2 Sample usage:
perl -x patchlevel.h "This is a custom patch"
=head1 Disabling known flapping tests
Some tests could fail under heavy load, whereas in most cases
they would simply succeed. Usually, continuous integration systems
will at one point or the other reach that problem.
To disable these known tests, please set the environment
variable CI to true.
CI=true
=cut
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。