Beefy Boxes and Bandwidth Generously Provided by pair Networks
There's more than one way to do things

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
On a Debian system that's not totally screwed up, parsing the output of dpkg -i is much easier than looking into /var/lib/dpkg/. There are environment variables which change the output format a bit, which you can exploit for your purposes. The man page knows more about that.
Or is there some other wrapper to a higher level API for this task?

I recommend looking at CPAN for that sort of question

Also, if anyone knows, is there some way to hook up my Perl script to be executed after whenever the package list changes?

There are hooks or triggers that are executed when packages are installed and removed (I think man-db uses that for its purposes). I'm not sure about the details, but looking into man-db or into the dpkg documentation should help.

If packages are installed via aptitude, you can also parse its log files.

In reply to Re: Walking Linux packages by moritz
in thread Walking Linux packages by tomazos

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

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.