Ok, I see your point, however the derived products will have to structle with the issue anyhow. So, I would prefer a strict lining to follow the targets that will affect on userland architecture and the decisions what projects are selected into core. In some cases even if they are experimental - The Meego is. However, I'm not experienced at all in how such is handled in other distros and though ok with the flow.
Thanks, -Teemu ________________________________________ From: Arjan van de Ven [[email protected]] Sent: Friday, December 03, 2010 5:10 PM To: Teemu Tuominen Cc: Laurent Pinchart; [email protected] Subject: Re: [Meego-kernel] About kernel-headers package in Meego (V4L2 subdev/Media Controller) On 12/3/2010 4:47 AM, Teemu Tuominen wrote: >> >> Anyway, we won't have the MC headers in the kernel-headers package in >> the near >> future, so a temporary media-controller-headers package might be needed. >> > Sounds like a decent temporary solution. I can take such task and > provide the specific headers package along with upcoming > gst-plugins-camera through the n900 device adaptation. If its > acceptable way to go - Arjan ? Maybe we should keep the solution > specific to Nokia N900 images as long as needed, but I feel its > necessity to gain focus and joint forces around Meego camera subsystem > contributors asap. Simply because it seems possible in near future. I'm not very happy about it.... you're going to get applications that use an ABI, and if the ABI changes in the upstreaming process, suddenly all your apps will break. until this is accepted by Linus, we really ought to not do this. Having a package as mentioned is ok if Linus already took the change, but did not make a release yet. But these ABIs aren't nearly that far yet. _______________________________________________ MeeGo-kernel mailing list [email protected] http://lists.meego.com/listinfo/meego-kernel
