Make libul{} rule match without hint

In the end, the extra jumping through the hoops doesn't justify the extra
safety we gain. The only plausible accidental mistake is making libul{} a
dependency of ./ but then we don't prevent the same for libue{}, which also
doesn't make much sense. Though, the consequences of doing this for libul{}
could be more severe, like messed up for-install'ness. Oh, well, I guess
people will just have to pay attention (this could be a good check for the
linter we've been thinking about).

1 files changed, 1 insertions, 5 deletions

diff --git a/libbuild2/bin/init.cxx b/libbuild2/bin/init.cxx
index 563a82f..2b1df97 100644
--- a/libbuild2/bin/init.cxx
+++ b/libbuild2/bin/init.cxx
@@ -29,8 +29,7 @@ namespace build2
   namespace bin
   {
     static const obj_rule obj_;
-    static const libul_rule libul_ (false);
-    static const libul_rule libul_metadata_ (true);
+    static const libul_rule libul_;
     static const lib_rule lib_;
     static const def_rule def_;
 
@@ -577,9 +576,6 @@ namespace build2
         r.insert<libul> (perform_update_id, "bin.libul", libul_);
         r.insert<libul> (perform_clean_id,  "bin.libul", libul_);
 
-        r.insert<libul> (perform_update_id, "bin.metadata", libul_metadata_);
-        r.insert<libul> (perform_clean_id,  "bin.metadata", libul_metadata_);
-
         // Similar to alias.
         //
         r.insert<lib> (perform_id,   0, "bin.lib", lib_);