On Sep 19, 2010, at 12:31, Carsten Munk wrote:
> 2010/9/19 Adrian Bunk <[email protected]>:
>>> Could I ask for how you would word the rules and at the same time,
>>> make this type of compliance testable by a machine? - keep the eye on
>>> the ball, MeeGo compliant applications that is stated as compliant for
>>> MeeGo version X, optionally only profile Y, must install without
>>> errors on MeeGo version X, profile Y if specified.
>>>
>>> Let's get a hands-on approach for this.
>>
>> I'd suggest to add library repositories:
>> - libraries in a library repository have to fulfill compliance rules
>> similar to applications
>> - a repository must specify which library repositories it uses
>> - a library can only be in one repository (unless it changed the soname)
>>
>
> Right - I agree with the first 2, but the third one is difficult, how
> can you prove it's only in one repository?
>
> I'm thinking compliance only allowed based on signature and a central
> API registry with public keys/certificates..
How on earth will you do that? That doesn't sound like something that will
scale.
Jeremiah
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
