Hi, On 08/26/2010 12:30 AM, ext Carsten Munk wrote: > libjpeg6b-dev (replacable by a open solution without harming ABI) > > OpenGL ES / EGL libs + headers (replaceable by Mesa, we do this in > MeeGo) - currently using SGX libraries
Alright, good that we get into details. Am I wrong or these components are problematic in general (at least for the ARM architecture) and not only for Maemo 5? What are the alternatives pure MeeGo is offering today? If the MeeGo stack is not offering solid OSS components then vendors need to find alternatives and the developers will need to rely on what is on the devices anyways. What is the answer of the MeeGo project? It's a good question but afaiu it goes beyond Maemo support alone. This is not my area of expertise, but libjpeg OSS development is moving towards libjpeg-turbo. Then the libjpeg6b-dev is a problem today but likely to vanish in the near future, is that right? What is the impact of having or not SGX/Mesa in the OBS? And again, is this a problem only for Maemo & Harmattan-MeeGo or just for any MeeGo Arm implementation to come before there is a good OSS replacement to SGX? > > So, it is technically possible. However, a exact API list is needed. > Does http://bugs.meego.com/showdependencytree.cgi?id=2719&hide_resolved=0 > correspond? Interesting question and very interesting link. :) Someone at meego-sdk should be able to answer this (afaik nobody in the Governance pages is assigned to own API/SDK). > However, downside of this: > > * It won't be possible to move extras-{testing,devel} from maemo.org > to OBS, which may hinder adaptation. There is some dissent against > current setup of extras anyway, so a fresh look on process and content > might be good anyway. OK, this is the argument of the one time exception to the Maemo community in order to ease and speed their integration to the MeeGo project. > * People won't be able to build against Hildon / Maemo 5 specific APIs. We would need to look deeper here as well. Some of these APIs belong to OSS components an in theory they could be part of the non-official libraries supported by the community in MeeGo - a different discussion. What are the relevant Maemo specific APIs that belong to close components? > * There won't be a community builder for Maemo 6 specific APIs. The discussion about MeeGo-Harmattan (provisional name for what was called Maemo 6 before the MeeGo launch) integration with MeeGo services hasn't started yet. There are no community apps being developed for MeeGo-Harmattan at this point and, as opposed to Maemo 5, there is no legacy to consider. We have the chance to define the community rules now. A default recommendation good for MeeGo and good for open source development is to support only the MeeGo official API in the MeeGo-Harmattan target in the community OBS. Good for app developers, good for the developers of those APIs, good for users and good for MeeGo. If someone wants to play with closed toolkits or APIs specific of a vendor (Nokia, Adobe, you name it) then they must use the SDK specific to them. This might be the case as well of the developers calling directly the SGX libraries. > * Someone has to do the work of getting a M5 target ('free' + > replacement closed bits) that provides a similar-to-MeeGo API target. > And whoever maintains Qt for M5 would have to collaborate with this > effort. > > Upside: > > * We can run a MeeGo extras repository that targets M5, M6 and MeeGo. > at same time People doesn't seem afraid to add extras-devel anyway, so > why not MeeGo extras.. Iw the MeeGo OBS provides any kind of Maemo target this should be the approach anyway: meego-extras is the default Extras and only those apps that can't build there "for legacy reasons" would go to maemo-extras. > * The OBS won't be tainted with closed source dependencies and no EULA > needed to build for M5 as well. The really ugly part is the EULA and we need to look exactly which components would require it. Actually the Maemo-MeeGo transition might be a compelling argument to open them. -- Quim _______________________________________________ MeeGo-community mailing list [email protected] http://lists.meego.com/listinfo/meego-community
