Re^5: ActiveState and Config.pm Question

I think you misunderstand what Dave is saying. When Perl builds, it creates the Config.pm module. There is no maintainer; it's an autogenerated file.

If you read the first two lines of the module, they allude to this. Perhaps there's a better way to explain what's going on there, but I can't think of a situation where Config would break after a normal installation process.

Comment on Re^5: ActiveState and Config.pm Question Select or Download Code

Replies are listed 'Best First'.
Re^6: ActiveState and Config.pm Question by Limbic~Region (Chancellor) on Jul 01, 2005 at 19:02 UTC
chromatic, I certainly was. So then this problem really should be address with ActiveState then. When you download their zip file (look ma - no installation), you get a Config.pm with entries in the hash containing: `C:\TEMP\perl-------------------------------------------please-run-the-install-script------------------------------------------\bin` It isn't that I should expect something that hasn't been installed to be psychic to know where you have installed it, but it could do a better job of explaining the problem. FWIW - I looked for an install script or some documentation on what to do to fix this and came up with nothing. I suppose I have to educate myself on the Config process now just so I won't make such an obvious oversight again. Cheers and thanks for clarifying. Cheers - L~R	[reply] [d/l]
Re^7: ActiveState and Config.pm Question by dave_the_m (Monsignor) on Jul 01, 2005 at 19:41 UTC
Ah, now I understand. That code in Config.pm isn't part of std perl, its something that ActiveState must have added. Yes, it's definitely something you'd have to raise with them rather than via perlbug. NB - you can use perlbug to report a bug in something like CGI.pm; anything that's bundled in the core becomes our responsibility (although we're likely to pass the report straight onto the author for fixing ;-) Dave.	[reply]