Subject: Re: crossreferencing .broken files?
To: Brook Milligan <email@example.com>
From: None <firstname.lastname@example.org>
Date: 12/18/2001 20:22:57
On Tue, 18 Dec 2001, Brook Milligan wrote:
> It occurred to me as I was browsing through the output of a bulk build
> that it might be useful for the .broken files to crossreference each
> other via a link. For example, when a package is marked "broken" and
> the .broken file is copied into the pkgstat directory, it would seem
> that lines like
> BULK> py-expect-1.9b1 (devel/py-expect) is broken because it depends upon tcl-expect-5.33.0 (lang/tcl-expect) which is broken.
> could be modified to add a link for part of the "depends upon ..."
> clause. Then, one could start with a package marked as "broken
> depends" and trace directly the chain of depends back to the root
> cause just be following the links in the .broken files. This might
> make the bulk build output more useful.
> Is this a useful idea, or would the extra clutter of links in the
> .broken files make it worse.
thats not a bad thought. I'll see about trying it out on my next bulk
build and see how it looks. It may not happen until after the 1st of the
year though unless someone else picks it up.