Make autobuild actually capable of, well, autobuilding

[ermo]

Had a quick discussion with Joey today:

ermo
is that your own rebuild script...?
(or a variation of the KDE one?)
Joey Riches
ah it's rebuild-template-script.sh in common/
it's never been as good since we've moved to monorepo ffiw
ermo
did you get tired of using autobuild and chasing down cycles?
Joey Riches
nah i used autobuild to generate the order
ermo
coolio
then it's at least seeing some use
Joey Riches
correct me if i'm wrong but i don't think autobuild can actually autobuild yet?
ideally i just bump all the rebuilds i want and autobuild builds them in order
ermo
it can only push them to the Solus builder in order
in practice, you probably want it to build and push them to a pre-defined local repo in order.
which means it probably needs to grow a notion of a "handler"
where the handler can be "build on build server", build on Solus, build on Serpent.
which then has a series of "build && push" templates.
you know go-task build <some profile> && sudo mv *.eopkg <the relevant local repo> && solbuild index <the relevant local repo>
or just build && sudo mv *.stone <the relevant local repo> && moss index <the relevant local repo>
Joey Riches
yep
possibly using a custom local repo instead of the generic one
ermo
where I suppose that the latter part is akin to "publish-to-target-repo".
where target repo is possibly defined as a custom profile
so you could, for e.g icu rebuilds, use -p icu-x86_64-local.profile for instance
(since at some point, we'll likely begin also offering ARM builds, so having the arch be part of the profile name from the outset seems wise)