From f9fae6dc8fb8783745be9d4ff914d5f67bab9dbc Mon Sep 17 00:00:00 2001
From: Jelle van der Waa <jvanderwaa@redhat.com>
Date: Fri, 22 Nov 2024 16:29:14 +0100
Subject: [PATCH] doc: enable python bridge related package documentation

The Python bridge is already the default bridge in our project and the C
bridge was removed in 7c7ab45e3f2d4bd11a4e5c6.
---
 doc/guide/packages.xml | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/doc/guide/packages.xml b/doc/guide/packages.xml
index 8a6f086f7e9a..33ed4bc1b281 100644
--- a/doc/guide/packages.xml
+++ b/doc/guide/packages.xml
@@ -108,7 +108,6 @@ $ cockpit-bridge --packages
           where there are conflicts. For example given two packages with the same
           <code>name</code> a package is chosen based on its priority.</para></listitem>
       </varlistentry>
-      <!-- TODO: enable this once moving to the Python bridge by default; also update example below
       <varlistentry>
         <term>conditions</term>
         <listitem><para>An optional list of <code>{"predicate": "value"}</code> objects. Cockpit will only
@@ -117,7 +116,6 @@ $ cockpit-bridge --packages
           This is preferable to using <code>priority</code>, but only available since Cockpit FIXME-RELEASE.</para>
         </listitem>
       </varlistentry>
-      -->
       <varlistentry>
         <term>requires</term>
         <listitem><para>An optional JSON object that contains a <code>"cockpit"</code>
@@ -262,7 +260,6 @@ $ cockpit-bridge --packages
 }
 </programlisting>
 
-<!-- TODO: enable this once moving to the Python bridge by default
 <programlisting>
 {
   "version": 0,
@@ -282,7 +279,6 @@ $ cockpit-bridge --packages
   }
 }
 </programlisting>
--->
 
   </section>