summaryrefslogtreecommitdiff
path: root/lib/perlbug.t
diff options
context:
space:
mode:
authorNiko Tyni <ntyni@debian.org>2016-04-25 16:31:00 +0300
committerAaron Crane <arc@cpan.org>2016-05-16 13:31:40 +0100
commitc04bead1edb16804f93c1d95979abf8e7477363a (patch)
tree378526285dec60164a3fdb5d26ffd69fec36f68c /lib/perlbug.t
parentbd18aea6d95681e1bd5c2cdfd894bd3706e4b819 (diff)
downloadperl-c04bead1edb16804f93c1d95979abf8e7477363a.tar.gz
perlbug: wrap overly long lines
Mail transport agents limit the length of message lines at SMTP time. One observed limit is 1000 characters per line. Mail user agents typically work around these limits by MIME-encoding the message. Since perlbug doesn't do that, it needs to limit the length of its lines manually to make sure bug reports get delivered. The longest lines in perlbug reports normally come from Config::myconfig output, particularly 'config_args', which has been observed to exceed 1000 characters on some configurations, causing report rejection. While less likely, the list of local patches is another potential source of overly long lines. Use Text::Wrap (if available) to wrap the body of the report at an arbitrarily chosen and hopefully safe limit of 900 characters. No indentation or continuation line markers are added, though it would be easy to add those if desired. Attachments and mail headers are not wrapped. Bug-Debian: https://bugs.debian.org/822463
Diffstat (limited to 'lib/perlbug.t')
-rw-r--r--lib/perlbug.t3
1 files changed, 0 insertions, 3 deletions
diff --git a/lib/perlbug.t b/lib/perlbug.t
index ede26af6d6..ed32c044f3 100644
--- a/lib/perlbug.t
+++ b/lib/perlbug.t
@@ -151,8 +151,5 @@ for (split(/\n/, $contents)) {
$maxlen1 = $len if $len > $maxlen1 and !/$B/;
$maxlen2 = $len if $len > $maxlen2 and /$B/;
}
-TODO: {
-local $::TODO = 'long body lines not wrapped yet';
ok($maxlen1 < 1000, "[perl #128020] long body lines are wrapped: maxlen $maxlen1");
-}
ok($maxlen2 > 1000, "long attachment lines are not wrapped: maxlen $maxlen2");