From 28ae8f90b3c7c5a5fa9b7749af5f5690fc4fb294 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Wed, 27 Mar 2013 13:07:22 -0700 Subject: [PATCH] ref-manual: Minor edits to "Packaging - package*.bbclass". (From yocto-docs rev: b6d4fe49442039cacc07224c68d4df0e6996ff43) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/ref-manual/ref-classes.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/documentation/ref-manual/ref-classes.xml b/documentation/ref-manual/ref-classes.xml index f9a1771d16..41a663394a 100644 --- a/documentation/ref-manual/ref-classes.xml +++ b/documentation/ref-manual/ref-classes.xml @@ -335,13 +335,13 @@ the fact that it processes more metadata. For example, this information includes individual file types, file checksum generation and evaluation on install, sparse file support, conflict detection and resolution - for multilib systems, ACID style upgrade, and repackaging abilities for rollbacks. + for Multilib systems, ACID style upgrade, and repackaging abilities for rollbacks. Another consideration for packages built using the RPM package manager is space. For smaller systems, the extra space used for the Berkley Database and the amount - of metadata can affect your ability to do on-device upgrades. + of metadata can affect your ability to perform on-device upgrades.