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.
  • I don't think this will work out well with the tools we have.

    Let me explain: The default installation paths for the traditional Perl resources are taken from the compile-time %Config hash. This includes various paths for modules and their binary parts, but no concept of user directories, /var/www or any other resources.

    Naturally, %Config being populated on perl-compile time cannot and should not provide this information. But scanning the system File::HomeDir-esque during installation and making guesses on b
    • Worse yet is asking the user during installation of a CPAN module. These kinds of questions are what makes the lives of sysadmins and cpan testers alike miserable.

      What you need is the installation of some tool in the bindir which can complete the installation. Taking the same approach that e.g. kwiki or rails takes. It does involve packaging all the assets into a Perl module somehow and then extracting them. In fact, a framework that does this might well be a useful CPAN module...

      -Dom

    • There are at least a few methods for leveraging "their binary parts".

      File::ShareDir is built entirely on it. It installs files into the /auto/ lib area.

      While I agree that teaching the CPAN infrastructure about the other resource types is likely to be impossible, I'm not entirely sure that asking the user is necesarily a bad idea.

      We already let users override the installation paths via things like PREFIX. So in principle the concept of user-driven configuration is not necesarily a bad idea, particularly on s
  • What I normally do in this case, is make sure I can set up a web application using a single script. This script involves a relatively simple call to the constructor of the main module (inherited from CGI::Application or whatever) with some params, and then calling its run() method (and exiting). Then I put an Apache alias to the script to serve it under a certain location.

    The application is self-contained and is aware of everything it needs, and is entirely hosted on the URL that it was placed on. This