[maemo-commits] [maemo-commits] r16523 - projects/haf/doc/mvo

[From: subversion at stage.maemo.org]

Author: marivoll
Date: 2008-10-29 02:14:02 +0200 (Wed, 29 Oct 2008)
New Revision: 16523

Modified:
   projects/haf/doc/mvo/system-model-2.txt
Log:


Modified: projects/haf/doc/mvo/system-model-2.txt
===================================================================
--- projects/haf/doc/mvo/system-model-2.txt	2008-10-28 23:51:13 UTC (rev 16522)
+++ projects/haf/doc/mvo/system-model-2.txt	2008-10-29 00:14:02 UTC (rev 16523)
@@ -177,9 +177,9 @@
 Most packages in the Maemo archive are part of one or more
 "Distributions".  The distributions are used to keep different lines
 of development separate from each other.  There is a 'stable' line of
-development that has been released for general consumption and only
-receives bug fixes.  There is also a 'testing' line that contains beta
-releases for developers and daring testers.
+development that has been released for general consumption.  There is
+also a 'testing' line that contains beta releases for developers and
+daring testers.
 
 Packages can be copied from one distribution to another in order to
 release them.  When copying packages, one or more source packages are
@@ -224,17 +224,19 @@
 Compatibility is important because packages (and groups of packages)
 are released independently.  Consider a typical 3rd party application
 in the extras category: they are meant to be installed 'immediately'
-on devices that run the current harmattan distribution, not on devices
-that run harmattan-testing.  Still, they are compiled in a
-harmattan-testing environment.
+on devices that run the current harmattan distribution.  They are not
+targeted at users running harmattan-testing, and they don't want to
+wait until their dependencies have been released.  Still, they are
+compiled in a harmattan-testing environment.
 
-Problems with this will arise when a binary package automatically
+Problems with this will only arise when a binary package automatically
 picks up a incorrect run-time dependency that is not satisfiable in
 harmattan.  The correct dependency would be satisfiable in harmattan,
-but the build tools used to compute it will not produce it.
+but the build tools used to compute it did not produce the correct
+result.
 
-These problems need to be solved by fixing things so that the correct
-run-time dependencies are computed during build time.
+These problems need to be solved by simply computing the correct
+run-time dependencies during build time.
 
 [ In other words, problems will arise when the interface management is
   too conservative.  We will make unrelated packages suffer in order
@@ -305,6 +307,10 @@
 everyone once per hour or so whenever there is a package in
 harmattan-proposed-updates.
 
+*** Snapshots
+
+[...]
+
 *** Continuity
 
 The Maemo archive can and should contain the distributions for
@@ -326,6 +332,14 @@
   keys?
 ]
 
+** Expiration
+
+The previous sections have described how new packages are added to the
+Maemo archive and how they move around.  There also needs to be a
+mechanism to expire old packages.
+
+[...]
+
 * Installation targets
 
 The Maemo OS runs on a number of devices.  It is installed via one or