I would structure your code this way: 
sub do_pkg_need_from_Dist {
  my ($Distdb, $rq_nam, $rq_vr, $rq_op, $Need_msg) = @_;
  my $newpkg;
  ... set $newpkg here ...;
  return $newpkg;
}

sub process_need_from_Dist {
  my $Need_msg = sub { ... };
  my $newpkg;
  ...
  if ($rq_nam) {
    $newpkg = do_pkg_need_from_Dist(..., $Need_msg);
  } else {
    $newpkg = $Distdb->find_rpm_owning_file_to_pkg($need);
    if ($newpkg) {
      $newpkg->add(...);
    } else {
      Serious ...;
    }
  }
}

[download]

In reply to Re^3: Perl scoping not logical...? by pc88mxer
in thread Perl scoping not logical...? by perl-diddler

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.