When to bundle libs with the python package?

As brought up in #18, it would be good to have a guidline as to when to pacakge a C ib with its python wrapper, and when to package it separately.

It seems to me the guideline is that if a lib is used by more than one package than it should be independently packaged -- i.e. libjpeg, libpng, etc..

On the other hand, there are python packages that tightly bind a given lib, and keeping them total in sync has its advantages -- i.e. pyproj bundles proj4, even though proj4 is used by gdal, etc. as well. (and is a useful command line tool)

So maybe we need to simply follow the original authors lead here. (though some packages have different bundling policies on Windows than LInux). ANd we may be able to influnece the package as well.

For example, by py_gd package wraps libgd:

https://github.com/NOAA-ORR-ERD/py_gd

as lib_gd is generally available on *nix sytems (it's used by PHP, among other things), I decided to package the lib separately for conda:

https://github.com/NOAA-ORR-ERD/orr-conda-recipes/tree/master/libgd

but in practice, nothing else in conda is using it (though may some day..), and I used a recent libgd which is not in the Linux distros (at least not the ones more than 6 months old...)

so maybe it would be easier and more robust to simily bundle the lib and bindings together (and probably statically link them while I'm at at...)

(and not, these are not in conda-forge yet, but I would like to put them there)