On 11/11/2010 01:43 PM, Wichmann, Mats D wrote: > I expect you'll get divided opinions on that, let's see what the > reactions are.
That's exactly my worry. But it seems that if we're going to go there (to a world where "MeeGo" means a limited and focused API suite and not just another distro), it's important to get it right ahead of time and not rely on intuition. My fear is that going ahead with the current API set is going to mean a ton of "assumed compatible" apps which dependencies on stuff that other people want to drop or change. Basically, everyone's intuition of what an "obvious" set of base features is will be different. FWIW, here's mine. I just quickly went through the list of MeeGo base packages in the current compliance spec and pulled out a list of the ones that provide important and common capabilities that I don't see abstracted in the current API set (or where I see a compelling reason to not want to use a wrapper API): bash bzip2 coreutils curl glibc gnupg grep openssl pcre sed zlib Andy -- MTS, MeeGo Solutions, Wind River Systems [email protected] _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
