Re: Keeping Glib up to date (was RE: Diablo, do we need a separate repository?)

2008-05-07 Thread Quim Gil
ext Graham Cobb wrote: Nokia should be keeping all system libraries up to date and should be scheduling testing, to verify that the updated libraries do not break anything, as part of the release cycle. It is part of Nokia's responsibilities to its development community. Sure, and

Keeping Glib up to date (was RE: Diablo, do we need a separate repository?)

2008-05-06 Thread Graham Cobb
On Tuesday 06 May 2008 13:32:34 [EMAIL PROTECTED] wrote: A properly versioned operating system should be able to handle side by side libraries. Why on earth bother? I am also not a DD but my understanding was that in Debian this was only done when some ABI change occurs and means an

Re: Keeping Glib up to date (was RE: Diablo, do we need a separate repository?)

2008-05-06 Thread Fred Labrosse
On Tuesday 06 May 2008, Graham Cobb wrote: To take a real example, I previously supported Opensync on mistral, gregale, bora and chinook. I have already abandonned support for all except chinook because it was too much effort to deal with the old glib versions. For the moment I persevere

RE: Keeping Glib up to date (was RE: Diablo, do we need a separate repository?)

2008-05-06 Thread josh.soref
That said, to some extent people obviously do want to use later versions of libraries when/where possible. No one loves the idea of using code that's many years out of date with its ever growing set of known bugs. However sometimes bug-wise compatibility triumphs. Graham Cobb wrote: