The Problems of Perl: The Future of Bugzilla
Christopher Hicks
chicks at chicks.net
Sat May 12 19:00:05 UTC 2007
On Sat, May 12, 2007 at 09:27:00AM -0400, David Miller wrote:
> Our end-users seem to detest external dependencies, so we
> always have to evaluate how much bang we're getting out of a perl module
> before adding it, and if it's a wheel that's ridiculously easy to
> reinvent, we probably will, to avoid the dependency. If it's a mature
> module with lots of bang for the effort (it will actually save us a lot
> of time writing code) then we'll probably use it.
Why make the end user pay the tax? Package all the modules we need with the bugzilla distro. This is how Krang and Twiki operate to varying degrees. Whining about the failures of Perl's module system when we're not doing what works well for other groups shipping Perl web applications seems a bit strange to me.
I'm not sure what scripts and tools krang and twiki use to maintain their own lib trees, but it can't be harder to write than dealing with all of the end user complaints.
--
</chris>
"The problem with troubleshooting is that trouble shoots back!"
More information about the developers
mailing list