Re^2: The App:: namespace? Sharing a webapp on CPAN

in reply to Re: The App:: namespace? Sharing a webapp on CPAN
in thread The App:: namespace? Sharing a webapp on CPAN

An advantage to using CPAN for a Perl application distribution (as if it were a module) would be the way CPAN.org automatically enables a logged-in user to use the annotation feature for a module's POD, and the way it ties into CPAN RT bug tracking for the module.

And the Kobes CPAN search site provides other goodies: an easy link to the CPAN ratings system and the automatic creation of a discussion board at CPAN::Forum.

Comment on Re^2: The App:: namespace? Sharing a webapp on CPAN

Replies are listed 'Best First'.
Re^3: The App:: namespace? Sharing a webapp on CPAN by dragonchild (Archbishop) on May 09, 2008 at 20:32 UTC
Given that I tend to ignore these things for both apps and modules, I don't really follow the benefit. But, if others like it, that's cool. The biggest problem I see is that CPAN is built for installing modules. There's a lot more to installing an application. Take a look at how Trac installs for what I consider to be the bare minimum. Applications, frankly, should be installed in a single click. You don't do that from CPAN. Maybe someone should write a ports interface to CPAN. My criteria for good software: Does it work? Can someone else come in, make a change, and be reasonably certain no bugs were introduced?	[reply]
Re^3: The App:: namespace? Sharing a webapp on CPAN by bingos (Vicar) on May 11, 2008 at 08:20 UTC
And don't forget the automated quality assurance of your application's test-suite being run on multiple perl versions and machine architectures by the CPAN Testers.	[reply]

In Section Seekers of Perl Wisdom