Tadman, thank you for your reply.
This looks like the direction we will want to move to with future releases.
The problem I am having with our dot .profile configuration files is that they are actually ksh scripts (determining ports, etc) and not just a list of keys and values. I cannot actually determine what values they will produce until install time when the files are in the target directory and they are actually sourced.
I don't like this design, but I am thinking of sourcing the dot configuration files in a ksh script and then calling a Perl script that wraps the make process.
Or, at install time, should I source the dot configuration files in a ksh script that then writes the environment to a "frozen" file, read the "frozen environment" and then put the key/value pairs in the Perl environment hash? And then call make in the "thawed" environment?
These solutions still feel somewhat awkward.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.