.framework bundles contain header files which are also included when then framework is shipped. For instance, apps using Growl.framework end up installing the framework along with the app. This comes will all the headers and versioning foo, leading to bloat in download size.
Do most of you OSX developers end up cleaning the .framework included with your apps to remove un-needed files, or is this considered bad practice for some reason?
Applescript to print Word documents
How to include the sqlite3 library “libsqlite3.0.dylib” in my application source file?
Get stdout and stderr from jar tool bundled for OSX
I would expect that this is the reason why framework creators don't particularly worry about this detail.
Getting involved with the Mac developer community [closed]
For example, in Python, the framework will contain what "make install" puts into the installation, so you get the same set of headers in the framework as you do in a regular Unix installation..
Why is IB changing the object IDs when opening a xib file?
Programmatically add an alias to the Dock in OS X
Find all PPC libraries, binaries and applications in Snow Leopard
shell script to link specific files up one level
The way I see it, most people have fast enough internet connections to handle downloading a little bit of extra data, and hard drive space is cheap.. If no one ever wants to look at the headers, then you've wasted a little bit of space.
However, if you strip the headers and someone, for whatever reason, does want to look at them, there's no way to get them back.
I'd rather provide something unnecessary rather than intentionally take away something that someone might want eventually..