[Catalyst-dev] [RFC] Remove (development) manual from C::Runtime

Jonathan Rockway jon at jrock.us
Sat Sep 23 00:10:45 CEST 2006


I'd like to split Catalyst::Manual and Catalyst::Manual::Tutorial into
their own separate CPAN dists.  Two reasons for this:

1) Fixing typos (etc.) in the Manual or Tutorial shouldn't affect
Catalyst::Runtime or Catalyst::Devel.  It would be nice to be able to
keep docs on search.cpan as up-to-date as possible, even when there's no
need for a core release.

2) I'd like to maintain C::M::T separately, so it can be bundled with
the necessary modules.

Here's my plan for what prereqs will looks like (nested modules are
depended on by their parent):

* C::Runtime
* C::Devel
 - C::Manual
* Task::Catalyst::Tutorial
 - C::Manual::Tutorial

I'd sort of like to combine T::C::T and C::M::T, since it makes sense to
install as one unit.  This will increase the "agility", as well.  If we
fix a typo, we can bump the versions of the required modules at the same
time.  The disadvantage of this approach is that we can't bundle the
tutorial with C::D, since installing C::D will bring in unnecessary modules.

Also, I have no problem acting as the documentation pumpking, unless
someone else really wants to handle that.

Regards,
Jonathan Rockway



More information about the Catalyst-dev mailing list