Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Array-Columnize CPAN distribution.

Report information
The Basics
Id: 71954
Status: resolved
Priority: 0/
Queue: Array-Columnize

People
Owner: Rocky Bernstein (no email address)
Requestors: SHLOMIF [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: v0.3.5
Fixed in: (no value)



Subject: The distribution contains the generated file "Makefile", and also does not display the POD
Hi! I'm trying to build Devel-Trepan and wanted to prepare this distribution for the Mageia Linux packages' repository. The Array-Columnize distribution contains the generated file "Makefile" which interferes with some Makefile.PL things, and, furthermore, the POD for the module is not displayed on http://search.cpan.org/dist/Array-Columnize/ (I.e: there is no link there). Please fix these issues. Regards, -- Shlomi Fish
First, let me thank you for attempting to package this. Second, I really am enjoying "The Enemy and How I Helped to Fight it" A sysadmin principle: Never ascribe to maliciousness that which can easily explained by oversight and ignorance. (I'm not suggesting you did, just that I'm a bit ignorant - and that's why I work on debuggers.) If you could suggest how to fix these problems, I'd be more than happy to make them. Fork he project and submit a merge request or attach a patch here. Or verbiage with a lot of hand waving will probably do as well too. The README problem is a war going on between github and CPAN. (Okay that's too strong according to the "sysadmin principle". It's just an incompatibility probably from ignorance.) To make things look nice on github one uses some sort of formatting; here it was markdown. (In other projects it was textile and I've used POD in the past and github now supports that.) If the README file is just README, github doesn't pick up formatting. See Perl-Devel-Trepan for example which I think does use POD. But CPAN on the other hand seems to only look for README, not README.md Does it handle README.textile or README.pod? Perl-Device-Cdio seems to look nice both on CPAN and github. I'm not sure how I managed to do that. Will investigate I think somewhere I also tried copying README.md to README in building the tarball. I'm not sure if that's a good thing. Suggestions?
Hi Rocky, On Sat Oct 29 09:54:34 2011, ROCKY wrote: Show quoted text
> First, let me thank you for attempting to package this. >
You're welcome. Show quoted text
> Second, I really am enjoying "The Enemy and How I Helped to Fight it" >
I'm glad you do. If you like it enough after you finish it, I would appreciate it if you recommend it on various social-linking/blogging/etc. sites: http://www.shlomifish.org/meta/how-to-help/ You may also enjoy the other resources on my site. Show quoted text
> A sysadmin principle: Never ascribe to maliciousness that which can > easily explained by oversight and ignorance. (I'm not suggesting you > did, just that I'm a bit ignorant - and that's why I work on > debuggers.)
Very well. I don't think I took into consideration why the problems were present there - I just noticed that they were. Show quoted text
> > If you could suggest how to fix these problems, I'd be more than happy > to make them. Fork he project and submit a merge request or attach a > patch here. Or verbiage with a lot of hand waving will probably do as > well too.
I've sent you a pull request on github. There are still some things left for you to do, like fill in the missing POD (in lib/Array/Columnize.pm) and fixing a problem in the README. Show quoted text
> > The README problem is a war going on between github and CPAN. (Okay > that's too strong according to the "sysadmin principle". It's just an > incompatibility probably from ignorance.) To make things look nice on > github one uses some sort of formatting; here it was markdown. (In > other > projects it was textile and I've used POD in the past and github now > supports that.) If the README file is just README, github doesn't pick > up formatting. See Perl-Devel-Trepan for example which I think does > use > POD.
I wasn't referring to the README, I referred to the inline POD in the lib/*.pm files which is handled by doing "perldoc Array::Columnize" and displayed as HTML in search.cpan.org metacpan.org, etc. Regards, Shlomi Fish Show quoted text
> > But CPAN on the other hand seems to only look for README, not > README.md > Does it handle README.textile or README.pod? Perl-Device-Cdio seems > to > look nice both on CPAN and github. I'm not sure how I managed to do > that. Will investigate > > I think somewhere I also tried copying README.md to README in building > the tarball. I'm not sure if that's a good thing. Suggestions? >
Basically fixed by the reporter following the principle that f you want something done right, you do it yourself. Version 0.38 released.