[Esbox-commits] r1992 - branches/work_Ed/org.maemo.esbox.help/html/tasks

[eswartz at garage.maemo.org]

Author: eswartz
Date: 2009-08-21 22:59:13 +0300 (Fri, 21 Aug 2009)
New Revision: 1992

Modified:
   branches/work_Ed/org.maemo.esbox.help/html/tasks/ValidatingPackages.html
Log:
Explain what a package validation message means

Modified: branches/work_Ed/org.maemo.esbox.help/html/tasks/ValidatingPackages.html
===================================================================
--- branches/work_Ed/org.maemo.esbox.help/html/tasks/ValidatingPackages.html	2009-08-21 17:14:19 UTC (rev 1991)
+++ branches/work_Ed/org.maemo.esbox.help/html/tasks/ValidatingPackages.html	2009-08-21 19:59:13 UTC (rev 1992)
@@ -61,6 +61,36 @@
 	<p/>
 	<img src="../images/validate/wiz-validate-4-log.png"></p>
 	</li>
+	<li><b>Troubleshooting:</b>
+		<ul>
+			<li>"The following build packages could not be mapped to known runtime or development packages"
+				<p>Build packages are <strong>pkg-config</strong> package entries which reference 
+				the compile-time and link-time flags for a package.  These are not the same as
+				Debian apt packages (which are called "system", "runtime", or "development" packages).
+				</p>
+				<p>Mica has a database, created at some point before release, containing a
+				mapping so it can accurately define which Debian package will provide the <strong>pkg-config</strong>
+				package.  So "known" only relates to the knowledge encoded there.
+				</p>
+				<p>This message primarily means that the database inside Mica is out of date, or that the
+				repositories did not contain information about these packages at the time the database
+				was created.
+				</p>
+				<p>There's no way to easily update this database without modifying Mica
+				(at this time), so these messages indicate that the package validator does not
+				know whether or not the necessary build-time support is installed.
+				</p>
+				<p>
+				To find the necessary package, use <tt>apt-cache search &lt;basename&gt;</tt> in the Scratchbox console, where
+				<strong>basename</strong> is the part of the name without "lib" or "-&lt;version&gt;", etc.
+				to find likely development packages.  Usually these are named "...-dev".  Then use
+				<tt>fakeroot apt-get install ...&lt;basename&gt;...-dev</tt> to install the necessary
+				development headers and libraries. 
+				</p>
+			</li>
+		</ul>
+	</li>
+	
 </ol>
 
 </body>