Changes between Version 13 and Version 14 of PortfileRecipes

Timestamp:

Jan 1, 2010, 9:51:03 AM (14 years ago)

Author:

ryandesign (Ryan Carsten Schmidt)

Comment:

total rewrite of variant_isset section

PortfileRecipes

@@ -49 +49 @@
 
 
-== variant_isset doesn't work when variant is set == #variant_isset
-Make sure you have the variant defined, even if it is empty, in the Portfile.  If all you need is to do something when the variant is set and not dedicate an entire variant section to it, variant_isset can work but you must still define the variant (or platform for things like darwin, darwin_9, etc).  So just add
-{{{
-variant myvariant {
-}
-}}}
-or
-{{{
-platform darwin 9 {
-}
-}}}
-Then port will set the variant when selected and variant_isset should work.
-
+== variant_isset requires the variant to exist == #variant_isset
+Normally you write the code for a variant inside the variant declaration:
+
+{{{
+variant my_variant description {Variant description} {
+    ...
+    post-destroot {
+        [post-destroot code for when the variant is set]
+    }
+}
+}}}
+
+Sometimes it's more natural to include the variant's code in other sections of the Portfile by checking if the variant is (or is not) set:
+
+{{{
+post-destroot {
+    ...
+    if {![variant_isset my_variant]} {
+        [post-destroot code for when the variant is not set]
+    }
+}
+}}}
+
+This is fine, but if you do it this way, you must ensure the variant is still defined in your Portfile, even if it is empty:
+
+{{{
+variant my_variant description {Variant description} {}
+}}}
 
 == Preferred use of default_variants == #default_variants