Re: Generate Config.pm for distribution in a package?

Okay, I'm afraid I don't understand your question here. (By the lack of responses, I reckon you've confused others, too. :) If you are building perl for bundling with your product targetted to, say AIX, won't you implicitly get the correct Config.pm for inclusion with the AIX build?

mhoward - at - hattmoward.org

Comment on Re: Generate Config.pm for distribution in a package?

Replies are listed 'Best First'.
Re^2: (jptxs) Generate Config.pm for distribution in a package? by jptxs (Curate) on Apr 06, 2005 at 11:21 UTC
Config.pm seems to be more subtle than that. It makes distinctions between different shades of AIX (different kernel settings, paramters, compilers, etc.) that the larger software package we distribute does not. In other words, Config.pm demands a greater level of specificty than any other part of our software package. So even if we generated a Config.pm for each server we build on in our labs, that would not cover the diversity of servers our software may eventually be installed on. I hope that helps clarify. It's starting to seem that there is no solution other than a brute force one (genrating a great deal of possible Config.pm files and putting them all in a directory structure that's addressed dynamically based on local configuration). We speak the way we breathe. --Fugazi	[reply]

Replies are listed 'Best First'.

Re^2: (jptxs) Generate Config.pm for distribution in a package?
by jptxs (Curate) on Apr 06, 2005 at 11:21 UTC

Config.pm seems to be more subtle than that. It makes distinctions between different shades of AIX (different kernel settings, paramters, compilers, etc.) that the larger software package we distribute does not. In other words, Config.pm demands a greater level of specificty than any other part of our software package. So even if we generated a Config.pm for each server we build on in our labs, that would not cover the diversity of servers our software may eventually be installed on. I hope that helps clarify.

It's starting to seem that there is no solution other than a brute force one (genrating a great deal of possible Config.pm files and putting them all in a directory structure that's addressed dynamically based on local configuration).

We speak the way we breathe. --Fugazi

[reply]