summaryrefslogtreecommitdiff
path: root/doc/libsolv.3
diff options
context:
space:
mode:
Diffstat (limited to 'doc/libsolv.3')
-rw-r--r--doc/libsolv.39
1 files changed, 7 insertions, 2 deletions
diff --git a/doc/libsolv.3 b/doc/libsolv.3
index 5d7e2c6..88180b9 100644
--- a/doc/libsolv.3
+++ b/doc/libsolv.3
@@ -2,12 +2,12 @@
.\" Title: Libsolv
.\" Author: [see the "Author" section]
.\" Generator: DocBook XSL Stylesheets v1.76.1 <http://docbook.sf.net/>
-.\" Date: 06/12/2013
+.\" Date: 06/14/2013
.\" Manual: LIBSOLV
.\" Source: libsolv
.\" Language: English
.\"
-.TH "LIBSOLV" "3" "06/12/2013" "libsolv" "LIBSOLV"
+.TH "LIBSOLV" "3" "06/14/2013" "libsolv" "LIBSOLV"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
@@ -47,6 +47,11 @@ fixed Ids for often used strings
.RS 4
access libsolv from perl/python/ruby
.RE
+.PP
+\fBlibsolv\-pool\fR
+.RS 4
+libsolv\(cqs pool object
+.RE
.SH "POINTER VALIDITY"
.sp
Note that all pointers to objects that have an Id have only a limited validity period, with the exception of Repo pointers\&. There are only guaranteed to be valid until a new object of that type is added or an object of that type is removed\&. Thus pointers to Solvable objects are only valid until another solvable is created, because adding a Solvable may relocate the Pool\(cqs Solvable array\&. This is also true for Pool strings, you should use solv_strdup() to create a copy of the string if you want to use it at some later time\&. You should use the Ids in the code and not the pointers, except for short times where you know that the pointer is safe\&.