# New Ticket Created by James Keenan
# Please include the string: [perl #45479]
# in the subject line of all future correspondence about this issue.
# <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=45479 >
It was only today that I became aware of the existence of the file
config/gen/PodText.pm. Here is an excerpt from its POD:
NAME
config/gen/PodText.pm - generate plain text docs from Pod files
SYNOPSIS
use gen::PodText;
gen::PodText->runstep($conf,
"source1.pod" => "dest1.pod"
"source2.pod" => "dest2.pod"
);
I have no quarrel with this module, but I suspect it is in the wrong
place in the Parrot distribution. All other *.pm files in config/
gen/ hold code for generating files as the final part of the Parrot
configuration process. Example: config/gen/makefiles.pm corresponds
to configuration step gen::makefiles. There is, however, no
configuration step called gen::PodText.
Moreover, it appears that config/gen/PodText.pm is not invoked by any
other file in the distribution.
[parrot] 507 $ fns . | xargs grep -l PodText
./config/gen/PodText.pm
./MANIFEST
Since all the real coding on this package was done before I joined
the project, I may not be fully aware of its rationale. Was it once
a configuration step, but then dropped? Is it meant to be an
optional configuration step?
Would we be better off by reformulating it as a Parrot developer's
tool (a program under tools/dev)?
Enlightenment sought. Thank you very much.
kid51
