Skip Menu |

This queue is for tickets about the Catalyst-Manual CPAN distribution.

Report information
The Basics
Id: 38713
Status: resolved
Priority: 0/
Queue: Catalyst-Manual

People
Owner: Nobody in particular
Requestors: EWILHELM [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 5.7013
Fixed in: (no value)



Subject: add links to Catalyst::Manual
From http://catalystframework.org/ the "Documentation" link goes straight to http://search.cpan.org/perldoc?Catalyst::Manual, which means that this pod would likely be the first thing a potential new user would see when trying to determine "so, what is this thing?". The Catalyst/Manual.pm should contain more L<> references so that the user has something on which to click. Probably this means something like a table-of-contents (similar to what you see at "http://search.cpan.org/dist/Catalyst-Manual/", but ordered for optimal introductoryism.) --Eric
Fixed. The correct solution is to link to the correct catalyst::manual in the catalyst::runtime distribution. There is some complexity caused by splitting out separate ::Runtime ::Devel and ::Manual dists. Hopefully this is the last in a long line of bugs on this theme.
On Mon Aug 25 18:02:38 2008, ZARQUON wrote: Show quoted text
> Fixed. The correct solution is to link to the correct catalyst::manual > in the catalyst::runtime distribution. There is some complexity caused > by splitting out separate ::Runtime ::Devel and ::Manual dists. > Hopefully this is the last in a long line of bugs on this theme.
Oops, revision is at http://dev.catalystframework.org/svnweb/Catalyst/revision?rev=8287
On Mon Aug 25 18:03:13 2008, ZARQUON wrote: Show quoted text
> On Mon Aug 25 18:02:38 2008, ZARQUON wrote:
> > Fixed. The correct solution is to link to the correct catalyst::manual > > in the catalyst::runtime distribution. There is some complexity caused > > by splitting out separate ::Runtime ::Devel and ::Manual dists. > > Hopefully this is the last in a long line of bugs on this theme.
> > > Oops, revision is at > http://dev.catalystframework.org/svnweb/Catalyst/revision?rev=8287
double oops, the correct revision is http://dev.catalystframework.org/svnweb/Catalyst/revision?rev=8288
On Mon Aug 25 18:02:38 2008, ZARQUON wrote: Show quoted text
> Fixed. The correct solution is to link to the correct >catalyst::manual in the catalyst::runtime distribution.
Well, that fixes the link from the catalystframework site, but anyone who lands on the Catalyst-Manual version of Catalyst::Manual is still going to be left scratching their head (and even more confusing there are two Catalyst/Manual.pm files!? Either get the indexer straight or something (I suspect that the .pm file causes trouble, especially with the new one not bearing a $VERSION.) In short, still not fixed: http://search.cpan.org/search?module=Catalyst%3A%3AManual
From: janus [...] errornet.de
On Mon Aug 25 18:18:10 2008, EWILHELM wrote: Show quoted text
> On Mon Aug 25 18:02:38 2008, ZARQUON wrote:
> > Fixed. The correct solution is to link to the correct > >catalyst::manual in the catalyst::runtime distribution.
> > Well, that fixes the link from the catalystframework site, but anyone > who lands on the Catalyst-Manual version of Catalyst::Manual is still > going to be left scratching their head (and even more confusing there > are two Catalyst/Manual.pm files!? Either get the indexer straight or > something (I suspect that the .pm file causes trouble, especially with > the new one not bearing a $VERSION.) > > In short, still not fixed: > > http://search.cpan.org/search?module=Catalyst%3A%3AManual
I totally agree, especially from a porters point of view where you have to decide for one of those two Manual.pm's to avoid conflicts in the resulting packages. So it's definitely not ppm's problem like written in the changelog.
See: http://dev.catalystframework.org/svnweb/Catalyst/revision?rev=9343 Hopefully that represents enough in the way of getting started links to not leave new users stranded.