Hmm...interesting idea. It would be sort of like distributing a C program as a statically linked binary. There are some practical reasons why that might not work well, however. For one thing, the Perl/Tk module is really huge, and a modem user who already has it installed probably doesn't want to have to download it again. It would be sort of like telling everyone who downloads a Java app that they need to download Swing along with it, even if they already have Swing installed :-) | [reply] |
It may be large, but it's the best chance of getting a workable solution. I suppose you could host the modules on your website in the various forms needed then have your install script hit your website, that way you still have complete control but the download is slightly smaller for some people. But of course that solution still breaks some of the time and is pretty stupid.
People want a solution that Just Works. I seriously doubt people will care about the extra 10 minutes of downloading required to get these modules. If you really cared about those few who would care, simply post two versions "version 1 with all modules needed" "version 2 with install script" or something.
| [reply] |
For one thing, the Perl/Tk module is really huge, and a modem user who already has it installed probably doesn't want to have to download it again. It would be sort of like telling everyone who downloads a Java app that they need to download Swing along with it, even if they already have Swing installed :-)
So you would only provide the bundles and nothing else? In that case it wouldn't be practical for everybody.
| MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!" | | I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README). | | ** The third rule of perl club is a statement of fact: pod is sexy. |
| [reply] |