in reply to modules out of the box
The "Minivend" author started with the attitude you had: he had wanted to make a "turnkey" solution for end users, and needed some modules that perhaps were not commonly installed, so he had included frozen versions of them into his distribution, under the original names.
Well, time passed, and he didn't incorporate the latest version of those modules into his distribution, but it came time for me to install Minivend to test it to see if I wanted to do a column about it. Imagine my horror when Minivend uninstalled my more modern versions of those handful of central modules, and replaced them with his own downrev versions!
I immediately posted a note to his support list and to P5P warning people that "minivend is evil", and got some interesting responses, but mostly the P5P group sided with me: a distribution should not have private versions of public modules under the CPAN-registered name. This leaves him (and you) with two solutions:
The "Minivend" author learned his lesson, and now does the latter. I suggest you seriously look at doing the same. Do you really think a site can be self supporting if they can't even install a module or two from the CPAN? There is a support cost to using Open Source software, and part of it includes being able to include components. If they want Microsoft, they know where to get it. {grin}
-- Randal L. Schwartz, Perl hacker
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
RE: RE: modules out of the box
by knight (Friar) on Sep 05, 2000 at 19:30 UTC | |
by merlyn (Sage) on Sep 05, 2000 at 20:17 UTC |