[ostree] docs: overview: Explicitly call out dpkg/rpm
- From: Colin Walters <walters src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [ostree] docs: overview: Explicitly call out dpkg/rpm
- Date: Fri, 20 Jun 2014 17:41:09 +0000 (UTC)
commit 1b1e3a592eeeee9da351837d06c70cd506a9a5a7
Author: Colin Walters <walters verbum org>
Date: Fri Jun 20 10:11:42 2014 -0400
docs: overview: Explicitly call out dpkg/rpm
To be more clear that we don't handle "inventory".
doc/overview.xml | 12 +++++++-----
1 files changed, 7 insertions(+), 5 deletions(-)
---
diff --git a/doc/overview.xml b/doc/overview.xml
index 79763b5..f227306 100644
--- a/doc/overview.xml
+++ b/doc/overview.xml
@@ -40,11 +40,13 @@
<emphasis>complete</emphasis> (bootable) filesystem trees. It
has no built-in knowledge of how a given filesystem tree was
generated or the origin of individual files, or dependencies,
- descriptions of individual components. This means that, for
- example, if you are distributing software which is licensed
- under the GNU General Public License, the burden lies with the
- tool generating these filesystem trees to ensure sufficent
- metadata is included for compliance.
+ descriptions of individual components. Put another way, OSTree
+ only handles delivery and deployment; you will likely still want
+ to include inside each tree metadata about the individual
+ components that went into the tree. For example, a system
+ administrator may want to know what version of OpenSSL was
+ included in your tree, so you should support the equivalent of
+ <command>rpm -q</command> or <command>dpkg -L</command>.
</para>
<para>
The OSTree core emphasizes replicating read-only OS trees via
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]