in reply to ActiveState and Config.pm Question

I don't really understand your issue. Config.pm is specific to perl, the OS, the hardware and the compiler - it is autogenerated when perl is built, and includes all the configuration parameters determined when that perl was built.

Solaris-PerlGcc-1.3 is a red-herring: ignore it.

Dave.

Replies are listed 'Best First'.
Re^2: ActiveState and Config.pm Question
by Limbic~Region (Chancellor) on Jul 01, 2005 at 14:18 UTC
    dave_the_m,
    The issue is that I would like to contact the maintainer of Config.pm about making a specific error message a bit more friendly. In trying to track that individual down I found that it belongs to a bundle not making any sense. Typically you will see a core module belonging to the Perl bundle for that distribution or individually belonging to an author between releases. Neither is the case here. So I assume your advice would be to contact a pumpking then?

    Cheers - L~R

    I added the word specific in my original post WRT OS and compiler to clarify things
      It's part of the core, so use perlbug to file a report.

      Dave.

        dave_the_m,
        Ok. I know you are trying to help and I appreciate that, but what tells me that just because a module is in the core I should use perlbug to file a report against it? I certainly wouldn't have thought to do that if the problem was with CGI as I would have emailed Lincoln.

        I suspect that by not contacting the maintainer and sending a "this seems wrong to me" message to p5p - I will get every opinion in the book as to how to solve the problem with no action, no response at all, or a "wrong place kid" response.

        Since you are the only person replying to this thread - I just may do that. I don't really feel that strongly about it to fight for though. I just wanted to raise some awareness about how an error message could be more user friendly.

        Cheers - L~R

Re^2: ActiveState and Config.pm Question
by Limbic~Region (Chancellor) on Jul 01, 2005 at 19:05 UTC
    dave_the_m,
    Ok - I can see it now plain as day "it is autogenerated when perl is built". For some reason, my brain read that as "the blanks are filled in when perl is built but the template is already there" and not as "the module doesn't exist before the actual build process". This is an AS problem not a Config.pm issue. Thanks for your help even though your clue stick didn't appear to be working at first.

    Cheers - L~R