summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorStef Walter <stefw@gnome.org>2014-01-04 11:17:18 +0100
committerStef Walter <stefw@gnome.org>2014-01-04 11:17:18 +0100
commit66e8949b7bad4b1b298146c5faeee0955bc71ac5 (patch)
tree84513a9217aa6d0d5d61535b23b903c8cb1cd663 /docs
parent0257a681062e1721c269b703922815308014a91f (diff)
downloadlibsecret-66e8949b7bad4b1b298146c5faeee0955bc71ac5.tar.gz
Remove unstable vapi
Just use the main vapi, and expect people to define the relevant SECRET_WITH_UNSTABLE preprocessor macro. https://bugzilla.gnome.org/show_bug.cgi?id=721429
Diffstat (limited to 'docs')
-rw-r--r--docs/reference/libsecret/libsecret-using.sgml9
1 files changed, 4 insertions, 5 deletions
diff --git a/docs/reference/libsecret/libsecret-using.sgml b/docs/reference/libsecret/libsecret-using.sgml
index 0add7c9..d047f67 100644
--- a/docs/reference/libsecret/libsecret-using.sgml
+++ b/docs/reference/libsecret/libsecret-using.sgml
@@ -99,14 +99,13 @@ AM_VALAFLAGS = \
<para>
Some parts of the <application>libsecret</application> API are not yet stable.
-To use them you need use the <literal>libsecret-unstable</literal> package.
-The API contained in this package will change from time to time. Here's how
-you would do it:
+To use them you need to define the SECRET_WITH_UNSTABLE C preprocessor
+macro to use them, or else the build will fail:
</para>
<informalexample><programlisting>
-AM_VALAFLAGS = \
- --pkg=libsecret-unstable
+AM_CPPFLAGS = \
+ -DSECRET_WITH_UNSTABLE=1
</programlisting></informalexample>
</chapter>