[maemo-commits] [maemo-commits] r16913 - projects/haf/doc/mvo
From: subversion at stage.maemo.org subversion at stage.maemo.orgDate: Tue Dec 9 14:59:30 EET 2008
- Previous message: [maemo-commits] r16912 - projects/haf/doc/mvo
- Next message: [maemo-commits] r16914 - in projects/haf/trunk/gtk+: . debian
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Author: marivoll Date: 2008-12-09 14:59:30 +0200 (Tue, 09 Dec 2008) New Revision: 16913 Modified: projects/haf/doc/mvo/system-model-2.txt Log: Fixos. Modified: projects/haf/doc/mvo/system-model-2.txt =================================================================== --- projects/haf/doc/mvo/system-model-2.txt 2008-12-09 12:48:47 UTC (rev 16912) +++ projects/haf/doc/mvo/system-model-2.txt 2008-12-09 12:59:30 UTC (rev 16913) @@ -180,7 +180,7 @@ the Maemo archive (somehow) and available to tools. [ Versioning interfaces is ultimately not enough. The evolution of an - interafce can be time stamped with versions, but these time stamps + interface can be time stamped with versions, but these time stamps can not really express the impact the interface changes have on clients. Some kinds of interfaces, such as package interfaces (see below) put restrictions on how interfaces can evolve which might @@ -218,10 +218,10 @@ *** Package interface A package interface is a interface that is made available by -installing a specific package. Examples are shared libraries, header -files to compile against shared libraries, programs with well-known -names, or sets of data files such as translations. The name of the -package is the name of the interface. +installing a specific package. Examples are libraries, header files +to compile against shared libraries, programs with well-known names, +or sets of data files such as translations. The name of the package +is the name of the interface. Not all packages of a subsystem are automatically package interfaces for the purpose of this discussion. Only those packages need to be @@ -243,8 +243,8 @@ installing any one of the set of packages that "provide" the interface (in the sense of Debian policy). The name used in the Provides declaration is the name of the interface. Virtual package interface -names must be unique in the Maemo archvie and must not be the name of -any package. +names must be unique in the Maemo archive and must not be the name of +any real package. A subsystem should list those virtual package interfaces that it defines and that it maintains the documentation for. Both providers @@ -265,6 +265,10 @@ to extract this information from the source code somehow and put it into the packages. +Note that in this context, a "D-Bus interface" is a well-known bus +name of a connection, not the thing that is called "interface" in +D-Bus terminology. + *** File interface A configuration file modification interface ("file interface" for @@ -272,15 +276,16 @@ or directories. For example, dropping .desktop files into /usr/share/applications/hildon/ is a file interface. The well-known name of the file or directory is the name of the file interface. If -the file or directory name is not unique, it should be qualified via a -suffix of the form "#foo". +the file or directory name is not unique (because it is used by more +than one interface), it should be qualified via a suffix of the form +"#foo". A package is a provider of a file interface when it contributes information to the well-known file or directory. It is a client when -it reads information from it. A file interfaces is usually owned by +it reads information from it. A file interface is usually owned by the subsystem that contains its major client. -Like with D-Bus interfacex, providers and clients of file interfaces +Like with D-Bus interfaces, providers and clients of file interfaces are not readily identifiable by just looking at the packages. We should make some rules to make this reliable. @@ -319,7 +324,7 @@ - Plugins -A component that can accept plugins needsa to document two things: how +A component that can accept plugins needs to document two things: how plugins can be registered with the component, and how the plugins will be called. This is combined into one interface: the registration method decides what kind of interface it is, and the detailed
- Previous message: [maemo-commits] r16912 - projects/haf/doc/mvo
- Next message: [maemo-commits] r16914 - in projects/haf/trunk/gtk+: . debian
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]