Thank you so much - that is exactly what I am looking for.

I do need it ordered because I'm creating a Perl Tk UI that will read this setup file, allow users to modify it and write it back out...basically, creating a Suite installer outside of InstallShield. I'm thinking of using a NoteBook where the first tab will have a list of Products and Features with CheckBoxes. The other tabs will have the "Property = Value" info in a label Textbox fashion so they can change the values and write out a new setup.ini.

I will also have another script that can be run from the UI and cmdline for users without UI capabilities, that will just read the setup.ini, build the commands to run each install silently and run them...where obviously, order does not matter.

Still have to figure that one out - when running outside the UI, how do I determine what to install. I May have to add a Product="y|n", Feature="y|n" to the setup.ini file.

Thanks a bunch - I knew to use Arrays of Hashes but couldn't conceptualize it visually.

Boy do I have a lot to learn - who'd thunk to use an || in a Hash Key. Great stuff.

If anyone has a better solution...by all means, let me know.

In reply to Re^4: Reading Install type config file into hash by tmurnane
in thread Reading Install type config file into hash by tmurnane

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.