On Thu, Dec 12, 2013 at 06:50:31PM +0100, Phil Knirsch wrote:
Now, to figure our how the build chains for these packages look like
i've cobbled together a (really bad) hack using python and
repoclosure that basically takes a set of packages as an input
(actually a set of requirements) and then spits out consecutively
the groups of packages needed to build the previous ones, so
basically a reverse grouped build order:
Nifty. I have the intuition that there might be particular nodes where
something pulls in an innocuous-looking dependency that leads to an
explosion of build requirements. If so, I bet there's a graphical
visualization of this that will make them jump out....
--
Matthew Miller -- Fedora Project Architect -- <mattdm(a)fedoraproject.org>