Many dependencies (header files, etc) are not installed on the machine when one runs 'make paranoid install'.  The user is not notified of this until the failure occurs.  There is no way to list dependencies that garnome does not itself handle (usually by including in the bootstrap section).

I propose creating a means by which dependencies can be accounted for, even if garnome does not directly provide a means by which they may be installed.

The primary problem with this is that many garnome users do not have superuser access on the machine on which they are using garnome.

Another problem is that there is no canonical way to refer to a package that persists across all variants of all operating systems.  The closest I can think of is the filename of the .pc file used with pkg-config.

We also want to start receiving reports of when 'make paranoid-install' fails.  I further propose that garnome make use of bug-buddy to open a communication channel with our users.

Some tasks that must be completed in order to allow dependencies to be correctly handled are the following:

* determine platform and flavor, ie config.guess + /etc/debian_version
* create script to map missing package to dist. package name
* create standard way of defining dependency on package not included in bootstrap
* when non-bootstrap, not-installed package is missing, add to dist. package list