On Tue, Sep 1, 2009 at 8:40 PM, Adam Kennedy<adamkennedybac...@gmail.com> wrote:
> This is where I see the SDL CPAN package. You develop initially on the > CPAN version, then do packaging and testing targeting the > installed/packaged/bundled/all-in-one version. I think this is where we're getting messed up.... I don't think CPAN should have anything other than what is in the latest stable binary click-wrapped build... The way I look at development is: 1.) sdl-perl application developers & end users use either click wrapped, distro supplied, or CPAN built packages as per their preference, all of which are based on the latest stable branch in github. 2.) sdl-perl infrastructure developers use either a.) stable branch from github or b.) bleeding edge branch from github If we find a bug in stable and fix it, we push a new set of click-wrap & CPAN bundles, and hope that the downstream distros pick up our patches in their next release. Bleeding edge code simply does not belong in CPAN, not should it be expected to work as advertised for development purposes. I am personally not a big fan of CPAN, as it tends not to play nicely with others. But it is so entrenched in the Perl community, that is hard to avoid. What I would like to find a way to provide both developers and end users with an experience closer to what the python community enjoys, of just downloading the latest zip or installer and having it work. But it is always the trying to play nice with CPAN viewpoint that makes this harder than it needs to be. Dave -- -=-=-=-=-=-=-=-=-=-=- http://blog.dloh.org/
