Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Could you please please please make the download of the compiler optional. I don't wish to download the same multi-megabyte compiler package again and again for every little upgrade of this Perl distro.
    • The entire mandate of this distribution is that it comes with a compiler built in by default.

      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 a
      • The entire mandate of this distribution is that it comes with a compiler built in by default.The entire mandate of this distribution is that it comes with a compiler built in by default.

        I am talking about upgrades... You're not suggesting people should upgrade to ActivePerl, are you?

        I don't see an obvious way to do what you want

        Well, you could have a package with compiler, and the same package but without compiler, for the people who already have the latter.

        • I'm suggesting when people upgrade, we have no idea what will be different.

          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 preconfigured to work.

          As for the conversation below about release tarballs, I'll point out tarballs are not Active Directory deployable enterprise-wide. :)

          So there are no release tarballs, there are just .exe or .msi files.