On Saturday 4. September 2010 00.59.37 Wichmann, Mats D wrote: > There's a rough early version available on > http://wiki.meego.com/Quality/Compliance > > We'd like to ask for feeback on this at various levels, > the most important being the highest level: does it > get anywhere close to describing an implementation of > the basic principles, as presented most recently > at the TSC meeting: > > http://trac.tspre.org/meetbot/meego-meeting/2010/meego-meeting.2010-08-18-1 > 8.58.html (follow to "full logs" to see the discussion) > > and mainly the reference: > > http://wiki.meego.com/Technical_Steering_Group_meetings/Compliance_Update_8 > -18-10 [snip] > So I'm proposing we just follow up to this thread - > edits, questions, comments, etc.
Hi Mike
Question on the toolchain: why is using the same toolchain mandatory? Can't
someone use a different toolchain, provided all the necessary ABI & API
requirements are kept? Besides upgrades to gcc, there are three more competing
compilers that might be used and may or may not provide performance
improvements. An ODM may choose to use one or more of those in particular
packages, performance-critical sections, etc.
In my view, rebuilding the same package with an ABI-compatible compiler should
be allowed and not take the compliancy away.
Note that this does not, in any way, affect the requirement that the MeeGo Core
and the reference implementation be entirely buildable with the reference
toolchain.
On the ABI and API section, it looks to me that we're redefining what is
defined
elsewhere. Isn't there a document we can point to and include by reference,
like the LSB?
A quick note on the plugin part (lines 235 to 237): is this to allow a plugin
to have undefined symbols that are resolved by the executable itself (i.e.,
executable with -rydynamic)? In my experience, that's sloppy plugin work...
3.5 Default shell: why do we require bash? Can't we require just any Bourne-
shell compatible shell to be at /bin/sh?
On OpenGL/ES requirements: I recommend listing the minimum versions of the GL
specifications as well as mandatory extensions. I'm not very familiar with
OpenGL, but I understand from people who are that there are a couple of
extensions which are always present anyway (so code ends up depending on
them). I'd recommend listing all of them.
I'd like to see an OpenGL 2 / OpenGL ES 2 requirement, but that's not going
to happen...
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Senior Product Manager - Nokia, Qt Development Frameworks
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
