03 Feb 2003 18:13:53 -0600
Short answer: No, not ever.
libegg is explicitly unstable, and should not be distributed in shared
library form. Generally speaking, apps wishing to depend on experimental
libegg functionality copy in known working sources of the objects they
depend upon. It is already relatively easy to use the bindings generator
independently of Gtk#, so there's nothing stopping developers from
installing a *private* shared lib of the egg objects they use, and
setting up a binding internally in their project.
On Mon, 2003-02-03 at 17:45, George Farris wrote:
> Any chance of including libegg in the next release of gtk#? It would be
> really handy.
> George Farris <email@example.com>
> Gtk-sharp-list maillist - Gtkfirstname.lastname@example.org
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
-----END PGP SIGNATURE-----