diff options
| -rw-r--r-- | Distrib/BuilddStatus.mdwn | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/Distrib/BuilddStatus.mdwn b/Distrib/BuilddStatus.mdwn index 5be632dd..6867878f 100644 --- a/Distrib/BuilddStatus.mdwn +++ b/Distrib/BuilddStatus.mdwn @@ -39,3 +39,14 @@ Would that be OK? Aha, OK, sounds good to me. I'd like to try to get consensus on (at least) which direction to head before proceeding. Then it's the next step to get done the sed magic and building an HTML output from buildd. -- [[Main/GrantBow]] - 10 Jun 2002 + +I saw your posts on bug-hurd about this. Adding comments on each package would be a grgeat benefit, but would perhaps require some kind of automatic merging of the comments and new buildd outputs. Which could get messy, even for an avid sed /perl/awk/python/whatever-fu master. + +One idea around this could be to decouple the comments from the buildd output. Having a separate Wiki page for each package. Perhaps like this: + + Log for failed build of grub-client_0.3.0-3 (dist=unstable) BuilddGrubClientComments + Log for failed build of libapache-mod-auth-mysql_3.2-1 (dist=unstable) BuilddLibApacheModAuthMysqlComments + +... 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 |