dbus-glib - removing the generated bus method wrappers

[Havoc Pennington]

Thiago Macieira wrote:
> Which brings me to a point raised before: can we define a standard 
> installation dir for D-Bus interface files? We've got quite a few of them 
> in KDE already and we'd like to install them.
> 

I think someone just needs to think this through and add stuff to the 
spec. Some thoughts (all half-baked):

  - installed files should be like from Introspect(), which differ from 
the .xml files people are using to generate e.g. glib bindings. i.e. we 
don't want the "code generation hints" crap about what to name the C 
functions, or really anything binding-specific, IMO for a variety of 
reasons.

  - every other "big directory o' text files" we ever specified ended up 
needing some type of binary cache ...

  - when should people use these and when should they use introspection?
(my take: installed files are intended for "-devel packages" i.e. should 
not be expected to exist on a user's system, only for purposes of 
building static stuff)

  - maybe more broadly, just briefly note some of the use cases

But anyhow, it needs thinking through, writing up the thinking through, 
discussion, merge discussion into writeup, create patch for spec.

Havoc