Isn't this a job for the package manager? Is it not just a case of multiple versions of libraries? On May 29, 2013 8:33 PM, "Luposian" <luposian@xxxxxxx> wrote: > I have found, on several occasions, games I download off of Haikuware no > longer work on the latest nightlies. For anyone curious as to what > nightlies (downloaded from Haiku-Files) I'm referring to, I mean the > "supported" one... gcc2hybrid. All the rest are considered "unsupported". > > Given that it appears that Haiku has updated to a newer version of libjpeg > and libpng (and others , I'm sure), is this likely going to pass over to > the next Alpha? Everyone keeps telling me "use Alpha 4.1", but the problem > with that is, when Alpha 5 comes out, everything will be broken, that is > broken right now. > > So, my question is, how do we mitigate the "damage", that these updated > libraries and such are creating? Does Haiku try to create a type of > "backwards compatibility" or do you put the onus on the developers to > recompile their apps/games, etc. for the newer libraries? If they refuse, > there are going to be a lot of worthless games and apps (that rely on older > versions of the libs) that simply will not work anymore. And few > developers seem to make mention of what version of libraries their > games/apps use or require, as though it will never change... ever. > > BeOS was all about leaving legacy behind and oftentimes, in that effort, > things broke regularly between versions. This is not a problem , when > developers are on the ball and want to stay on the leading edge of > improvements. But if people are not alerted to the problems developing > now, in the nightlies, while it's still a relatively new problem, when > Alpha 5 comes out, the bomb is gonna drop and the casualties (in users, > software, and Haiku mindshare) will likely be significant. > > Should not the problem be address ASAP, rather than waiting til the next > Alpha, when everything breaks... big time... and in a very public way? > > >