Hi Peter, Werner wrote > Well, this *only* happens if you do a build from the git repository; > for this situation I still think that you should have all the tools.
It's long been tradition across free software that building a released tarball required less tools than grabbing the in-development source. A tarball would ship with a ./configure, etc., whilst in-*development* needed developer tools, and often particular versions given autoconf and friends' pickiness. I see no reason for groff to deviate from that norm, especially for small, generally useful, widely available packages like netpbm. How about a README.* for development that lists the typical packages needed for common platforms so the resources are just a single `apt-get install' away? Cheers, Ralph.
