From e3f077ba7584f65561e21ca195215abd341b9147 Mon Sep 17 00:00:00 2001
From: Boris Kolpackov <boris@codesynthesis.com>
Date: Mon, 7 Feb 2022 07:59:48 +0200
Subject: Add support for meta-operation wildcard in scope::insert_rule()

---
 build2/cli/init.cxx | 16 +++++-----------
 1 file changed, 5 insertions(+), 11 deletions(-)

(limited to 'build2/cli')

diff --git a/build2/cli/init.cxx b/build2/cli/init.cxx
index 2a07196..a00fd7f 100644
--- a/build2/cli/init.cxx
+++ b/build2/cli/init.cxx
@@ -246,6 +246,9 @@ namespace build2
 
       // Register our rules.
       //
+      // Other rules (e.g., cc::compile) may need to have the group members
+      // resolved/linked up. Looks like a general pattern: groups should
+      // resolve on *(update).
       {
         auto reg = [&rs, &m] (meta_operation_id mid, operation_id oid)
         {
@@ -255,17 +258,8 @@ namespace build2
           rs.insert_rule<cxx::ixx> (mid, oid, "cli.compile", m);
         };
 
-        reg (perform_id, update_id);
-        reg (perform_id, clean_id);
-
-        // Other rules (e.g., cc::compile) may need to have the group members
-        // resolved/linked up. Looks like a general pattern: groups should
-        // resolve on *(update).
-        //
-        // @@ meta-op wildcard?
-        //
-        reg (configure_id, update_id);
-        reg (dist_id, update_id);
+        reg (0 /* wildcard */, update_id);
+        reg (perform_id,       clean_id);
       }
 
       return true;
-- 
cgit v1.1