NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Compiler optional? (Score:2)
Re:Compiler optional? (Score:1)
If you do not want a compiler in your Perl distribution, ActiveState makes an excellent Win32 Perl distribution that can meet your needs.
Further, as dagolden mentions, "each little release" only applies during alpha, and I'm afraid we're going with simplicity here.
Once we get to production releases, we expect there to only be one release per Perl release. So it adds 10meg of extra download per 6 months.
I don't see an obvious way to do what you want, and achieve some of the other goals of the project, like making the package installable from Active Directory.
Reply to This
Parent
Re:Compiler optional? (Score:2)
I am talking about upgrades... You're not suggesting people should upgrade to ActivePerl, are you?
Well, you could have a package with compiler, and the same package but without compiler, for the people who already have the latter.
Re:Compiler optional? (Score:2)
Put a current release tarball (unpacked?) on an rsync server, and let rsync do its magic? Clearly this is only easy if someone has a suitable rsync server already set up.
Re:Compiler optional? (Score:1)
-Ken
Re:Compiler optional? (Score:1)
Re:Compiler optional? (Score:1)
Re:Compiler optional? (Score:1)
Re:Compiler optional? (Score:1)
In the last round, perl stayed the same, some files moved to different directories, a new version of dmake was bundled, IO from the core was upgraded and so on.
When you upgrade, you download again. It's once every 6 months or so, so it's no biggie for 90% of people.
We may well be able to do some sort of no-compiler version for experts, with a big caveat-emptor that we can't predict what will happen with a compiler we haven't preconfi