Skip Menu |

This queue is for tickets about the Dist-Zilla-Plugin-ReadmeAnyFromPod CPAN distribution.

Report information
The Basics
Id: 112004
Status: open
Priority: 0/
Queue: Dist-Zilla-Plugin-ReadmeAnyFromPod

People
Owner: Nobody in particular
Requestors: tlhackque [...] yahoo.com
Cc: ether [...] cpan.org
AdminCc:

Bug Information
Severity: Wishlist
Broken in: (no value)
Fixed in: (no value)



Subject: Conditional inclusion
Pod::Readme provides conditional inclusion of text. The documentation is a little hard to find, but if you install it and do a perldoc Pod::Readme it's there. Although it claims Pod::Readme as an ancestor, ReadmeAnyFromPod doesn't provide the same facility, which is quite useful. It would be ideal if it used the same syntax. (However, see https://github.com/bigpresh/Pod-Readme/issues for some issues :-) The short form is =begin :readme text is included =end :readme =for readme stop following pod goes in the doc, not the readme =for readme continue following pod goes in both =for readme include file=foo type={pod,text} start=regexp end=regexp file starting with and upto regexps (or whole file if omitted) is (er, should be) inserted as verbatim - that is, as if each line were POD beginning with a space. There should (used to be) the ability to select based on readme format. That's broken in the current Pod::Readme, but something like =begin :readme markdown =end :readme markdown =for readme stop format=markdown =for readme continue format=markdown should exist. (Why the =for version? Because it allows text common to doc and readme to be woven. It would be great if ReadmeAnyFromPod could have feature parity with Pod::Readme. Thanks for your consideration.
On Sat Feb 13 11:49:36 2016, tlhackque wrote: Show quoted text
> Pod::Readme provides conditional inclusion of text. > > The documentation is a little hard to find, but if you install it and > do a perldoc Pod::Readme it's there. > > Although it claims Pod::Readme as an ancestor, ReadmeAnyFromPod > doesn't provide the same facility, which is quite useful. > > It would be ideal if it used the same syntax. (However, see > https://github.com/bigpresh/Pod-Readme/issues for some issues :-) > > The short form is > > =begin :readme > text is included > =end :readme > > =for readme stop > > > following pod goes in the doc, not the readme > > =for readme continue > > following pod goes in both > > =for readme include file=foo type={pod,text} start=regexp end=regexp > > file starting with and upto regexps (or whole file if omitted) is > (er, should be) inserted as verbatim - that is, as if each line were > POD beginning with a space. > > There should (used to be) the ability to select based on readme > format. That's broken in the current Pod::Readme, but something like > > =begin :readme markdown > > =end :readme markdown > > =for readme stop format=markdown > > =for readme continue format=markdown > > should exist. (Why the =for version? Because it allows text common > to doc and readme to be woven. > > It would be great if ReadmeAnyFromPod could have feature parity with > Pod::Readme. > > Thanks for your consideration.
ReadmeAnyFromPod doesn't claim Pod::Readme as an ancestor. It was forked (with permission) from Dist::Zilla::Plugin::ReadmeFromPod, which was using Pod::Text at the time of the fork: https://github.com/fayland/dist-zilla-plugin-readmefrompod/blob/1921bd8551093f4102ff191de9b4b5ecc2d66e04/lib/Dist/Zilla/Plugin/ReadmeFromPod.pm#L17 It seems that ReadmeFromPod has since been updated with similar multi-format features to ReadmeAnyFromPod, in the process switching from Pod::Text to Pod::Readme, as seen here: https://github.com/fayland/dist-zilla-plugin-readmefrompod/commit/ced52e034cee6d85ab3fd821dcaf58cd09d22c5c I have not done any development on ReadmeAnyFromPod in a while, so I was not aware of this update until I started investigating the situation for this bug report. So obviously, ReadmeAnyFromPod does not use Pod::Readme. I suppose if you want a plugin that uses Pod::Readme, you could use ReadmeFromPod. Otherwise, if you submit a patch that makes ReadmeAnyFromPod work using Pod::Readme, I'll be happy to merge it if it passes the test suite.