Adding third-party code to Agaric's core site repository: Print module's PDF functionality

At Administer › Site configuration › Printer-friendly pages, the PDF tab will tell you:

No PDF generation tool found! Please dowload a supported PHP PDF generation tool. Check this module's INSTALL.txt for more details.

5:15:53 PM Benjamin Melançon: one of the real benefits of the git "central" repository will be the handful of modules that need third-party software installed in them to function. Is there any special approach to this we should take (it's one of the reasons I liked the CVS approach, same as with Drupal, being able to CVS update the entire codebase and leave sites/all intact), or is it likely something we'll have to just re-do each time we update a module's code?
5:18:45 PM Stefan Freudenberg: Explain some more, please.
5:19:06 PM Benjamin Melançon: take the print module for instance
5:19:34 PM Benjamin Melançon: for printing to PDF support, you must:
5:19:39 PM Benjamin Melançon: 1. Download dompdf from http://sourceforge.net/projects/dompdf/
2. Extract the contents of the downloaded package into the print module
directory (usually sites/all/modules/print)
5:19:50 PM Benjamin Melançon: and a little configuration
5:20:27 PM Benjamin Melançon: that should go into the print module in drupal-6-agaric-core
5:20:50 PM Benjamin Melançon: so we do the extra installation required once (and upgrades once), and git takes care of it from there
5:21:04 PM Benjamin Melançon: TinyMCE and some other modules will have the same need
5:22:10 PM Benjamin Melançon: just checking if i should try anything special to allow drush updates without having to re-fetch the third party code-- but then such code should be checked for updates anyway
5:22:51 PM Benjamin Melançon: " 4. Grant write access to the lib/fonts directory to your webserver user." --- git/capistrano will pass those along, right?
5:23:11 PM Stefan Freudenberg: yes
5:24:02 PM Benjamin Melançon: also i'll want to make our first modifications to the ROBOTS.txt we keep there-- adding no-follow commands for /print urls
5:24:42 PM Benjamin Melançon: I guess maybe the issue here is we should document this somewhere, heh

Resolution