I'm still not quite sure how to build or structure the tree, though. I was thinking of using a hash with each package name as a key as a way to avoid extra calls to the function to extract dependencies and to avoid getting a package's dependency tree twice (2 packages have a dependency on the same package):

my $deps = { 'mainpackage-1.0' => [ 'dependency1-1.3', 'dependency2-2.3', 'dependency3'], 'dependency1-1.3' => [ 'dep1_of_dep1' ], 'dependency2-2.3' => [ 'dep1_of_dep2', 'dep2_of_dep2', 'dep3_of_dep2' ], 'dependency3' => undef };

This way, I have easy access to each previously referenced packages's primary dependencies without another function call. I still can't figure out how to put it all together into a full dependency tree, though. I'm still not sure I'm going about this the right way.

In reply to Re: Re: building a dependency tree by agaffney
in thread building a dependency tree by agaffney

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.