On Thu, 2018-07-26 at 15:40 +0000, Jeff Johnson wrote:
There are easier ways to accomplish build ordering using tsort(1) and
a minor amount of scripting with the same simplifying assumptions your program is making:
1) no cycles
2) every package provides its own name
3) every package supplies prerequisite package names without versions
tsort(1) just needs 1 line of input for each package containing the name followed by a
list of prerequisites ending with a new line
More important than build ordering is scheduling a set of builds
efficiently across multiple build machines to complete in the
shortest amount of time taking into account the cost in memory and
cpu time of each package build.
This is a rather over-bold claim. What's "more important" depends on
what you're doing at the time. If you just need to bump and rebuild a
bunch of packages on Rawhide for an soname bump (just to give an
*ENTIRELY RANDOM EXAMPLE*, right juhp? :>), then a tool like this is
what you need. Since you won't be scheduling the builds - that's Koji's
job - you don't need a tool that does that.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net