packaging
/
ostree
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: overview: Explicitly call out dpkg/rpm 

To be more clear that we don't handle "inventory".
This commit is contained in:
Colin Walters 2014-06-20 10:11:42 -04:00
parent bb043b319f
commit 1b1e3a592e
1 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/overview.xml
View File

@ -40,11 +40,13 @@
<emphasis>complete</emphasis> (bootable) filesystem trees. It <emphasis>complete</emphasis> (bootable) filesystem trees. It
has no built-in knowledge of how a given filesystem tree was has no built-in knowledge of how a given filesystem tree was
generated or the origin of individual files, or dependencies, generated or the origin of individual files, or dependencies,
descriptions of individual components. This means that, for descriptions of individual components. Put another way, OSTree
example, if you are distributing software which is licensed only handles delivery and deployment; you will likely still want
under the GNU General Public License, the burden lies with the to include inside each tree metadata about the individual
tool generating these filesystem trees to ensure sufficent components that went into the tree. For example, a system
metadata is included for compliance. 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>
<para> <para>
The OSTree core emphasizes replicating read-only OS trees via The OSTree core emphasizes replicating read-only OS trees via