summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichal Suchanek <hramrach_L@centrum.cz>2002-09-09 15:33:00 +0000
committerMichal Suchanek <hramrach_L@centrum.cz>2002-09-09 15:33:00 +0000
commit401901e4bcfea6c8e99e86aabf9d9614089cde3b (patch)
treec8232a755298eeef8ba726d91a69dff148b31c17
parent234c7d9c923a846effbb491564863f48d347a951 (diff)
none
-rw-r--r--Distrib/BuilddStatus.mdwn15
1 files changed, 15 insertions, 0 deletions
diff --git a/Distrib/BuilddStatus.mdwn b/Distrib/BuilddStatus.mdwn
index 6867878f..08a141a4 100644
--- a/Distrib/BuilddStatus.mdwn
+++ b/Distrib/BuilddStatus.mdwn
@@ -50,3 +50,18 @@ One idea around this could be to decouple the comments from the buildd output. H
... or similar. One could even add simple markup to color failed packages red and successful builds green. The biggest issue, however, is the one dealing with commenting buildd results and merging new buildd results with these comments.
-- [[Main/JoachimNilsson]] - 10 Jun 2002
+
+It looks like you need no explicit merging if you just put a [[WikiWord]] for the packge in the end of buildd log line.
+
+But if you meant merging new results with old results I know only two ways:
+
+* Put it all in a hash in memory and update from new log
+* Store it in a database and update from the log
+
+For this you need
+
+1. parse buildd log to get date, package name, status
+2. either save into database or append to a text file
+3. process the updated database/text file
+
+Sounds easy to me. What am I missing?