> - 106-109: "System implementers MUST use the source code of the MeeGo > 1.1 Reference Implementation and SHALL NOT replace or omit Core or > Profile components." > > There are cases where a vendor might want to substitute equivalent > (read: identical API & ABI) components to take advantage of specific > platform features. Some examples of this might be codecs that run on > a DSP, hardware-accelerated SSL engines and so on. The substitute's > licence should also match the reference implementation's to avoid > unintentional issues with run-time linkage etc, but otherwise I think > this should be allowed.
On a limited basis; there's a reason why people have asked for "use the reference source", because otherwise you have to get into detailed behavioral descriptions and tests to be sure you haven't broken the ABI by replacing pieces. There's a flag in the draft about this - codecs might not be an applicable example, but specialized opengl libraries that go with a specific hardware/driver combination could be. I'm really uncomfortable with that as there's been more than one instance out in the wild of replaced gl drivers causing problems, missing interfaces, etc. - but I'm assuming that's a reality. I hope the replacement list will be small and possibly ought to be bounded in some way so that people don't end up surprised. > - 3.4 Interpreted languages > > IMHO the location of the site/vendor trees should also be standardised > here. Makes packaging extra modules unambiguous, plus similar > considerations as above. Sounds like a sensible suggestion. _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
