Re: GTK 2.0 for familiar

I'm not a programmer but wouldn't it be possible to go through
Familiar and produce some stats on what widgets are actually in use?
Then you could prune everything else, with perhaps a few included
because they're "likely to be used". Then you could package the other
widgets in small, specialised packages containing sensibly grouped
widgets (e.g., "special purpose", "deprecated") that are depended from
packages that require them.

That way you can keep the libgtk package small but not disallow use of
excluded widgets.

In addition, these changes should probably be propagated upstream to
the libgtk maintainers -- I'm sure familiar isn't the only place that
would need lightweight libraries.

-- 
Rev Simon Rumble <simon@rumble.net>
www.rumble.net
Send email with subject "send key pub" for public key.
Illegal arrivals by sea have always been a problem
in Australia.  Ask any Aborigine.
- corruption of a Robert Orben quote