Johan Dahlin wrote:
There are two options here. The first is to add the binding to pygtk or gnome-python. The second is to distribute a stand alone package.* How/Who do I send my work to?James, again, is there something for gnome-python?
The main benefit of including it in gnome-python is for wider distribution of the code.
Benefits of having a separate package is that you can make releases at your own pace (rather than waiting for a gnome-python release, for instance). Also, you can cause your package to error out during configure if GtkSourceView is not found (if it went into gnome-python, the configure script would most likely be set up to simply ignore the wrapper if GtkSourceView wasn't found).
It would also be worth looking at what kind of API stability guarantees are being given for GtkSourceView at the moment. If the API changes much, building as a separate package is probably the right answer at the moment.
James.
--
Email: [EMAIL PROTECTED] | Linux.conf.au http://linux.conf.au/
WWW: http://www.daa.com.au/~james/ | Jan 22-25 Perth, Western Australia.
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
