RE: RFC version issues



On Fri, 2004-01-23 at 04:15, Murray Cumming Comneon com wrote:
It sounds like gtk-perl compiles different stuff depending on what 
version of the dependencies are available. This does sound very 
confusing. I think that version x of gtk-perl (or anything) should 
have the same API and always the same API. If people want GTK+ 2.2 
instead of GTK+ 2.4 then they can use an older version of gtk-perl.

that would be more confusing than anything. we'd have to have 
a stable release for each and every gtk level.

For every major version, yes. There are not that many, and you typically
only need to support one unstable version and one stable version. That's
what we do for gtkmm.

Because GTK+ never breaks ABI, there is no reason why people can't upgrade
their GTK+ if they want to get new features or important bugfixes in newer
version of gtk-perl.

People will install gtk-perl from binaries. They will have no chance to do
any fancy configure stuff anyway. And you don't want different distros doing
different configure-time stuff so that each distro has gtk-perl binaries
that seem to have the same number that have different APIs.

This works for everyone else, and should work for gtk-perl.

[snip]
what does gtkmm does? this is/should be an issue for all of 
the binding sets not just gtk2-perl although i don't remember 
seeing anyone else even trying to handle it.  

gtkmm 2.0.x works with GTK+ 2.0, 2.2 and 2.4. It has the same API however
you configure it.
gtkmm 2.2.x works with GTK+ 2.2 and 2.4. It has the same API however you
configure it.
gtkmm 2.4.x will work with GTK+ 2.4. It has the same API however you
configure it.

We never had any complaints about that perfectly normal API policy.

Murray Cumming
www.murrayc.com
murrayc usa net



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]