aboutsummaryrefslogtreecommitdiff
path: root/clean
diff options
context:
space:
mode:
Diffstat (limited to 'clean')
-rw-r--r--clean/clean.cli4
-rw-r--r--clean/clean.cxx10
2 files changed, 10 insertions, 4 deletions
diff --git a/clean/clean.cli b/clean/clean.cli
index 3c710fe..d3be4d6 100644
--- a/clean/clean.cli
+++ b/clean/clean.cli
@@ -127,8 +127,8 @@ Fatal error.|
\li|\cb{2}
-An instance of \cb{brep-clean} or \l{brep-migrate(1)} is already running. Try
-again.|
+An instance of \cb{brep-clean} or some other \cb{brep} utility is already
+running. Try again.|
\li|\cb{3}
diff --git a/clean/clean.cxx b/clean/clean.cxx
index d7a7731..5401ab1 100644
--- a/clean/clean.cxx
+++ b/clean/clean.cxx
@@ -111,8 +111,8 @@ namespace brep
ops.db_port (),
"options='-c default_transaction_isolation=serializable'");
- // Prevent several brep-clean/migrate instances from updating build
- // database simultaneously.
+ // Prevent several brep utility instances from updating the database
+ // simultaneously.
//
database_lock l (db);
@@ -316,6 +316,12 @@ namespace brep
? i->second
: default_timeout);
+ // @@ Note that this approach doesn't consider the case when both
+ // the configuration and the package still exists but the package
+ // now excludes the configuration (configuration is now of the
+ // legacy class instead of the default class, etc). We should
+ // probably re-implement it in a way brep-monitor does it.
+ //
bool cleanup (
// Check that the build is not stale.
//