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.
  • The blog about this bug wasn't reporting it, it was highlighting the fact that RHEL *still* hadn't fixed it, and gave some interesting background, including links to the thread on the dbic list about it.

    We happen to be affected by this bug and it's really annoying - a 10% performance loss from ithreads isn't really an issue as our servers are almost entirely I/O or DB bound, adding DBIx::Class makes for sucky performance on the dev server, but fortunately our production servers don't have the problem.

    It's t

    --

    @JAPH = qw(Hacker Perl Another Just);
    print reverse @JAPH;
    • Do you really need to compile the modules on every box?

      For the project at work, we install almost all CPAN deps in an app specific directory under a local user account. Those files are version controlled together with the application source.

      Release basically consists of tarring up the source tree (including deps), and release is untarring things in the correct place and running a configuration script.

      If you have different architectures on your boxes this obviously won't work without some extra maneuvers.

      We do this for > 95% of the modules. Some modules are very difficult to install without being root, so they are dealth with separately on a host level.

      This approach leads to each deployment of all versions of all apps being almost entirely decoupled from each other. Otherwise any upgrade of any centrally installed CPAN module would reqiure a complete retest of, like, everything. Which wouldn't happen. Which would break things eventually.